Skip to content

← Actionable
Medium, CVSS 6.3amended

OGNL stricter-invocation block list bypass via java.lang.reflect reflection proxies

CVE-2026-113730GHSA-crwc-vw2r-qr6m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ognl:ognl 3.4.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Maven ognl:ognl

    Affected
    < 3.4.13
    Fixed in
    3.4.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-113730: 0.39% estimated exploitation activity in the next 30 days; percentile 33.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary OGNL's optional *stricter invocation* mode maintains a block list that prevents expressions from directly calling methods on dangerous classes such as `Runtime`, `ProcessBuilder`, and `ClassLoader`. The block list filters on the declaring class of the method OGNL invokes. Because `java.lang.reflect.Method` (and `Constructor`/`Field`) are not on the list, an expression can use reflection as a proxy — `someMethod.invoke(target, args)` — to reach a blocked method. The real call (e.g. `ProcessBuilder.start()`) then executes inside the JDK reflection machinery and never passes back through OGNL's `invokeMethod`, so the block list never sees it.

Proof of concept Under the default OGNL context (public-only access, stricter invocation enabled), the following expression creates a file even though a direct `new ProcessBuilder(...).start()` is blocked: ``` (#pb=new java.lang.ProcessBuilder({"/usr/bin/touch","rce-proof.txt"}),…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from osv record GHSA-crwc-vw2r-qr6m

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-crwc-vw2r-qr6m

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-crwc-vw2r-qr6m

  4. Revision 1 · created ·

    Published from osv record GHSA-crwc-vw2r-qr6m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113730

Advisory: OGNL stricter-invocation block list bypass via java.lang.reflect reflection proxies
IDs: CVE-2026-113730, GHSA-crwc-vw2r-qr6m
Record: https://patchnext.com/advisories/cve-2026-113730 (revision 4, source checked 3 Nov 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ognl:ognl 3.4.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven ognl:ognl: affected < 3.4.13; fixed in 3.4.13

## Suggested inspection (read-only)
- Maven ognl:ognl: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ognl:ognl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-crwc-vw2r-qr6m (OSV record GHSA-crwc-vw2r-qr6m lists affected ranges: Maven ognl:ognl >=0 <3.4.13 (fixed))
- Verified: https://github.com/advisories/GHSA-crwc-vw2r-qr6m (GitHub-reviewed advisory GHSA-crwc-vw2r-qr6m lists affected ranges: Maven ognl:ognl >=0 <=3.4.12)

Commands are suggestions: review each one before running it.

Loading voting…