November 14, 2026

CVE Watchtower

CVE-2026-113730Protection Mechanism Failure

NVDCVSS scored by security-advisories@github.com

Vulnerability Summary

OGNL is an Object Graph Navigation Library for Java. Prior to 3.4.13, the optional stricter-invocation mode in OgnlRuntime.invokeMethod checks the declaring class of the method that OGNL invokes but does not block java.lang.reflect.Method, java.lang.reflect.Constructor, or java.lang.reflect.Field. An attacker-controlled expression can invoke one of these reflection objects as a proxy for a method on a blocked class, causing the real operation to execute inside JDK reflection without passing through the stricter-invocation check again. Exploitation requires an application to evaluate untrusted OGNL expressions, use the default or an equivalently permissive MemberAccess that permits reflection, and rely on stricter invocation as a sandbox. Applications using a restrictive MemberAccess, including Apache Struts with SecurityMemberAccess, are not affected by this bypass. This issue is fixed in 3.4.13.
Severity Level
MEDIUM(5.6)
Published Date
Oct 20, 2026
Last Modified
Oct 22, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.39%Probability
Root Weakness (CWE)
CWE-693: Protection Mechanism Failure β†—
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks.
CVSS v3.1 Base Metrics — Score 5.6 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

Affected & Patched Versions

Affected Versions
Not provided by NVD for this CVE.
Patched Versions
No patched version published yet
Until a fix ships, reduce exposure:
  • Restrict access to the affected service or interface to trusted networks.
  • Disable the affected feature if you do not need it.
  • Watch the vendor advisory for a firmware or software update.

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run the affected product and which version.
  2. No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
  3. Subscribe to the vendor advisory so you learn when a fix ships.

Timeline

  • Oct 20, 2026Published
  • Oct 22, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get alerts for CVEs like this oneYou are reading CVE-2026-113730. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

External References

Data last checked: Nov 14, 2026 21:37 UTC