dbcve.org
Commons OgnlApplication · Apache

CVE-2025-53192

HIGH · 8.8 CVSS v3.1 Published 2025-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
** UNSUPPORTED WHEN ASSIGNED ** Improper Neutralization of Expression/Command Delimiters vulnerability in Apache Commons OGNL. This issue affects Apache Commons OGNL: all versions. When using the API Ognl.getValue​, the OGNL engine parses and evaluates the provided expression with powerful capabilities, including accessing and invoking related methods, etc. Although OgnlRuntime attempts to restrict certain dangerous classes and methods (such as java.lang.Runtime) through a blocklist, these restrictions are not comprehensive. Attackers may be able to bypass the restrictions by leveraging class objects that are not covered by the blocklist and potentially achieve arbitrary code execution. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Commons OGNL's Ognl.getValue API evaluates expressions with powerful capabilities but uses an incomplete blocklist to restrict dangerous classes like java.lang.Runtime. Attackers can bypass these restrictions by leveraging unblocked class objects to achieve arbitrary code execution.

MitigationSince Apache Commons OGNL is retired with no fix coming, immediately identify all OGNL usage, migrate to a supported expression library (e.g., MVEL, SpEL), or implement strict input validation/sandboxing and restrict access to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Commons OgnlApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Commons OGNL dependency
    Search your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR files in classpath) for 'commons-ognl' or 'org.apache.commons.ognl'
    Affected if The dependency is present in the project
  2. Locate Ognl.getValue usage
    Search your codebase for calls to Ognl.getValue, OgnlParser.getValue, or similar OGNL evaluation methods
    Affected if Code calls Ognl.getValue or related APIs
  3. Determine input source to OGNL evaluation
    Trace the data flow into Ognl.getValue calls - check if parameters come from HTTP requests, user input, configuration files, or other external sources
    Affected if Untrusted or user-controlled input can reach Ognl.getValue
  4. Check if OGNL evaluation is exposed to untrusted users
    Review authentication and authorization controls around code paths that invoke OGNL evaluation
    Affected if The OGNL evaluation endpoint or functionality is accessible to untrusted or unauthenticated users

If Apache Commons OGNL is present in the environment and untrusted input can flow to Ognl.getValue, the application is vulnerable to command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Apache Commons OGNL is retired with no fix coming, immediately identify all OGNL usage, migrate to a supported expression library (e.g., MVEL, SpEL), or implement strict input validation/sandboxing and restrict access to trusted users only.

Recommended fix High confidence
  1. Accept that Apache Commons OGNL is retired and no vendor fix will be released
  2. Identify all code dependencies on Commons Ognl across the codebase
  3. Evaluate and migrate to an actively maintained OGNL library alternative such as Apache Commons OGNL's successor projects, or replace OGNL expression evaluation with a safer alternative
  4. If migration is not immediately feasible, implement strict access controls: restrict who can submit OGNL expressions to the system, apply network-level filtering, and add application-layer validation/authorization before any Ognl.getValue() call
  5. Audit logging and monitoring should be enabled for any OGNL expression evaluation to detect exploitation attempts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commons Ognl Scoped from the published advisory
  • Consultation16.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA16.0 h
80.0 hours of engineering $14,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,784.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data