NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Remote code execution in Apache Commons ConfigurationGHSA-7qx4-pp76-vrqh

CRITICALFix: apache/commons-configuration@add7375

GHSA-7qx4-pp76-vrqh is a critical-severity (CVSS 10) vulnerability in org.apache.commons:commons-configuration2. A fix is available for org.apache.commons:commons-configuration2 — see the affected versions and patch details below.

Also known asCVE-2020-1953
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
6.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk
1.50%3.69%5.89%8.08%2.7%6.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.apache.commons:commons-configuration2

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

Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.commons:commons-configuration2≥ 2.2&&< 2.72.7org.apache.commons:commons-configuration2:2.7

Affected Products

3 products · 14 configurations
Application
commons configurationapache
5 versions
2.22.32.42.52.6
Application
database serveroracle
5 versions
11.2.0.412.1.0.212.2.0.118c19c
Application
healthcare foundationoracle
4 versions
7.1.17.2.07.2.17.3.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update org.apache.commons:commons-configuration2 to 2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7qx4-pp76-vrqh is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatImportant

Several packages are unaffected because they do not include support for YAML configurations: * `apache-commons-configuration` as shipped with Red Hat Enterprise Linux 7 * `apache-commons-configuration` as shipped with Red Hat Enterprise Virtualization * `rh-maven35-apache-commons-configuration` as shipped with Red Hat…

ProductFixed inAdvisory
Red Hat AMQcommons-configuration2RHSA-2020:3133
Red Hat AMQcommons-configuration2RHSA-2020:2751
Red Hat Fuse 7.7.0commons-configuration2RHSA-2020:3192

Frequently Asked Questions

Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.
O3 Security · Impact-Aware SCA

Is GHSA-7qx4-pp76-vrqh in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Remote code execution in Apache Commons Configuration