How severe is GHSA-pvp8-3xj6-8c6x?

No CVSS score has been assigned to GHSA-pvp8-3xj6-8c6x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pvp8-3xj6-8c6x?

GHSA-pvp8-3xj6-8c6x affects the following packages: commons-configuration:commons-configuration (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pvp8-3xj6-8c6x?

The records we use list no patched version of commons-configuration:commons-configuration for GHSA-pvp8-3xj6-8c6x. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-pvp8-3xj6-8c6x in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-configuration:commons-configuration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pvp8-3xj6-8c6x if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-pvp8-3xj6-8c6x actively exploited in the wild?

No public exploit code has been indexed for GHSA-pvp8-3xj6-8c6x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pvp8-3xj6-8c6x?

GHSA-pvp8-3xj6-8c6x has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pvp8-3xj6-8c6x?

GHSA-pvp8-3xj6-8c6x is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pvp8-3xj6-8c6x published, and has it been updated?

GHSA-pvp8-3xj6-8c6x was published on May 9, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Apache Commons Configuration Uncontrolled Resource ConsumptionGHSA-pvp8-3xj6-8c6x

GHSA-pvp8-3xj6-8c6x is a Uncontrolled Resource Consumption vulnerability in commons-configuration:commons-configuration. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2025-46392

Published

May 9, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pvp8-3xj6-8c6x.

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕commons-configuration:commons-configuration

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-configuration:commons-configuration`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

commons configurationapache

≥ 1.0 && < 2.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-configuration:commons-configuration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of commons-configuration:commons-configuration for GHSA-pvp8-3xj6-8c6x. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-pvp8-3xj6-8c6x (CC BY 4.0)

Frequently Asked Questions

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 scenarios 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,

O3 Security · Impact-Aware SCA

Is GHSA-pvp8-3xj6-8c6x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works