# CVE-2025-46392: Apache Commons Configuration: Uncontrolled Resource Consumption when loading untrusted configurations in 1.x

> Attackers can cause excessive resource consumption by loading untrusted configurations, requiring migration to version 2.x.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2025
- **Updated:** 13 May 2025
- **Also known as:** CLEANSTART-2026-RH95647, CLEANSTART-2026-UM71044, CLSA-2026-1791205000, CLSA-2026-1792010667, CLSA-2026-1792014556, DEBIAN-CVE-2025-46392, GHSA-pvp8-3xj6-8c6x, UBUNTU-CVE-2025-46392

## What is CVE-2025-46392?

CVE-2025-46392 is a medium-severity denial of service vulnerability in Apache Commons Configuration, published on 9 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Uncontrolled Resource Consumption vulnerability in Apache Commons Configuration 1.x.

There are a number of issues in Apache Commons Configuration 1.x that allow excessive resource consumption when loading untrusted configurations or using unexpected usage patterns. The Apache Commons Configuration team does not intend to fix these issues in 1.x. Apache Commons Configuration 1.x is still safe to use in scenario's where you only load trusted configurations. 

Users that load untrusted configurations or give attackers control over usage patterns are recommended to upgrade to the 2.x version line, which fixes these issues. Apache Commons Configuration 2.x is not a drop-in replacement, but as it uses a separate Maven groupId and Java package namespace they can be loaded side-by-side, making it possible to do a gradual migration.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including commons-configuration:commons-configuration. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `commons-configuration:commons-configuration` | Maven | All versions to 1.10 | None |
| `commons-configuration:commons-configuration` | Maven | All versions to 1.10 | None |

Products: Apache Commons Configuration.

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

Upgrade to a fixed version.

## Is CVE-2025-46392 being exploited?

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

## Other vulnerabilities in Apache Commons Configuration

- [CVE-2020-1953](https://insights.sbomify.com/CVE-2020-1953/): Remote code execution in Apache Commons Configuration (critical 10.0)
- [CVE-2022-33980](https://insights.sbomify.com/CVE-2022-33980/): Apache Commons Configuration insecure interpolation defaults (critical 9.8)
- [CVE-2024-29131](https://insights.sbomify.com/CVE-2024-29131/): Apache Commons Configuration: StackOverflowError adding property in AbstractListDelimiterHandler.flattenIterator() (high 7.3)
- [CVE-2024-29133](https://insights.sbomify.com/CVE-2024-29133/): Apache Commons Configuration: StackOverflowError calling ListDelimiterHandler.flatten(Object, int) with a cyclical object tree (medium 5.4)
- [CVE-2026-45205](https://insights.sbomify.com/CVE-2026-45205/): Apache Commons Configuration: StackOverflowError for YAML input with cycles (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46392 is a medium-severity denial of service vulnerability in Apache Commons Configuration, published on 9 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46392 in the wild and no public exploit code.

Affected packages and fixed versions:
- commons-configuration:commons-configuration (Maven): affected all versions up to 1.10; no fix listed
- commons-configuration:commons-configuration (Maven): affected all versions up to 1.10; no fix listed

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-46392/ (Markdown: https://insights.sbomify.com/CVE-2025-46392/index.md)
```

## Sources

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

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