# CVE-2025-53192: Apache Commons OGNL: Expression Injection leading to RCE

> Attackers can achieve arbitrary code execution by bypassing blocklist restrictions in the retired Apache Commons OGNL library during expression evaluation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Aug 2025
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-53192, GHSA-5vgh-76mj-8hcq, SUSE-SU-2025:03285-1, SUSE-SU-2025:3825-1, SUSE-SU-2025:3839-1, UBUNTU-CVE-2025-53192, openSUSE-SU-2025:15567-1, openSUSE-SU-2025:15568-1

## What is CVE-2025-53192?

CVE-2025-53192 is a high-severity code injection vulnerability in Apache Commons OGNL, published on 18 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

** 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.

Weakness: CWE-146 (Improper Neutralization of Expression/Command Delimiters)

## Which versions are affected by CVE-2025-53192?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `suse-manager-5.0-aarch64-proxy-httpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-aarch64-proxy-salt-broker-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-aarch64-proxy-squid-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-aarch64-proxy-ssh-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-aarch64-proxy-tftpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-httpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-ppc64le-proxy-salt-broker-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-ppc64le-proxy-squid-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-ssh-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-tftpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-httpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-s390x-proxy-salt-broker-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-s390x-proxy-squid-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-ssh-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-tftpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-httpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-x86_64-proxy-salt-broker-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-x86_64-proxy-squid-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-ssh-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-tftpd-image` | SUSE:Manager Proxy 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-aarch64-proxy-httpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-aarch64-proxy-salt-broker-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-aarch64-proxy-squid-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-aarch64-proxy-ssh-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-aarch64-proxy-tftpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-httpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-ppc64le-proxy-salt-broker-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-ppc64le-proxy-squid-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-ssh-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-ppc64le-proxy-tftpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-httpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-s390x-proxy-salt-broker-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-s390x-proxy-squid-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-ssh-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-s390x-proxy-tftpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-httpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.21 |
| `suse-manager-5.0-x86_64-proxy-salt-broker-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.26.21 |
| `suse-manager-5.0-x86_64-proxy-squid-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-ssh-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |
| `suse-manager-5.0-x86_64-proxy-tftpd-image` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.5.1-7.24.7 |

Products: Apache Commons Ognl.

## How do I fix CVE-2025-53192?

Product is end of life, replace it.

## Is CVE-2025-53192 being exploited?

There is no known exploitation of CVE-2025-53192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53192 and fix it if it is affected.

What it is: CVE-2025-53192 is a high-severity code injection vulnerability in Apache Commons OGNL, published on 18 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-53192 in the wild and no public exploit code.

Affected product: Apache Commons OGNL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53192/ (Markdown: https://insights.sbomify.com/CVE-2025-53192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53192
- OSV: https://osv.dev/vulnerability/CVE-2025-53192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53192/
Summaries are generated and may contain mistakes; the official description above is the record.
