Commons ConfigurationApplication · Apache
CVE-2025-46392
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 · uneditedUncontrolled 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.
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 confidenceApache Commons Configuration 1.x contains uncontrolled resource consumption vulnerabilities that allow excessive resource usage when loading untrusted configurations or using unexpected usage patterns. This is a denial-of-service style vulnerability that the maintainers have explicitly declined to fix in the 1.x branch.
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 ConfigurationApplication
>= 1.0, < 2.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Commons Configuration version in dependenciesInspect your project's build configuration (pom.xml, build.gradle) or the application's classpath for the commons-configuration library. Check if the version falls in the 1.x range (1.0 through 1.x). Use 'mvn dependency:tree' or examine META-INF/MANIFEST.MF in jar files.Affected if The application depends on commons-configuration version 1.x (1.0 through 1.x inclusive)
-
Identify configuration loading sourcesSearch the codebase for calls that load configurations - look for XMLConfiguration, PropertiesConfiguration, JSONConfiguration, ConfigurationFactory, or ConfigurationBuilder implementations. Check for file loading, URL loading, or stream-based configuration initialization.Affected if The application loads configurations from external or untrusted sources such as user-specified file paths, remote URLs, or unvalidated input streams
-
Review configuration file structure for recursive patternsExamine the configuration files being loaded. Look for include directives, variable interpolation with JNDI or system property lookups, CombinedConfiguration with multiple sources, or deep nesting that could trigger unbounded recursion during loading.Affected if Configuration files contain include statements, recursive variable interpolation, or composite configuration layers that could exhaust resources during parsing
You are affected if Apache Commons Configuration 1.x is present AND configurations are loaded from untrusted sources or use complex nested variable interpolation patterns
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.0
Upgrade to Apache Commons Configuration 2.x, which uses a separate Maven groupId and Java package namespace, allowing side-by-side deployment for gradual migration. Only load trusted configurations until the upgrade is complete.
Apache Commons Configuration 2.x (any 2.x release)
- 1. Identify all Maven dependencies or build configurations that reference Apache Commons Configuration 1.x (org.apache.commons:commons-configuration or similar)
- 2. Update the Maven dependency to use Commons Configuration 2.x by changing the groupId to org.apache.commons:commons-configuration2
- 3. Update all Java import statements from org.apache.commons.configuration.* to org.apache.commons.configuration2.* in your source code
- 4. Review API differences between 1.x and 2.x as they are not drop-in compatible
- 5. Test the application thoroughly after migration to ensure configuration loading still works as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Commons Configuration
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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