CVE-2025-48734 is a high-severity (CVSS 8.8) CWE-284 vulnerability in commons-beanutils:commons-beanutils. A fix is available for commons-beanutils:commons-beanutils — see the affected versions and patch details below.
Apache Commons Improper Access Control vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48734.
EPSS Exploitation Probability
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
commons-beanutils:commons-beanutils☕org.apache.commons:commons-beanutils2Real-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
Improper Access Control vulnerability in Apache Commons.
A special BeanIntrospector class was added in version 1.9.2. This can be used to stop attackers from using the declared class property of Java enum objects to get access to the classloader. However this protection was not enabled by default. PropertyUtilsBean (and consequently BeanUtilsBean) now disallows declared class level property access by default.
Releases 1.11.0 and 2.0.0-M2 address a potential security issue when accessing enum properties in an uncontrolled way. If an application using Commons BeanUtils passes property paths from an external source directly to the getProperty() method of PropertyUtilsBean, an attacker can access the enum’s class loader via the “declaredClass” property available on all Java “enum” objects. Accessing the enum’s “declaredClass” allows remote attackers to access the ClassLoader and execute arbitrary code. The same issue exists with PropertyUtilsBean.getNestedProperty(). Starting in versions 1.11.0 and 2.0.0-M2 a special BeanIntrospector suppresses the “declaredClass” property. Note that this new BeanIntrospector is enabled by default, but you can disable it to regain the old behavior; see section 2.5 of the user's guide and the unit tests.
This issue affects Apache Commons BeanUtils 1.x before 1.11.0, and 2.x before 2.0.0-M2.Users of the artifact commons-beanutils:commons-beanutils
1.x are recommended to upgrade to version 1.11.0, which fixes the issue.
Users of the artifact org.apache.commons:commons-beanutils2
2.x are recommended to upgrade to version 2.0.0-M2, which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | commons-beanutils:commons-beanutils | ≥ 1.0&&< 1.11.0 | 1.11.0commons-beanutils:commons-beanutils:1.11.0 |
| ☕Maven | org.apache.commons:commons-beanutils2 | ≥ 2.0.0-M1&&< 2.0.0-M2 | 2.0.0-M2org.apache.commons:commons-beanutils2:2.0.0-M2 |
Affected Products
commons beanutilsapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-beanutils:commons-beanutils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update commons-beanutils:commons-beanutils to 1.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48734 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
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.
This vulnerability is rated as important severity because a flaw exists in Apache Commons BeanUtils, where PropertyUtilsBean and BeanUtilsBean allow uncontrolled access to the declaredClass property of Java enum objects. Applications that pass untrusted property paths directly to getProperty() or getNestedProperty()…
| Product | Fixed in | Advisory |
|---|---|---|
| Cryostat 4 on RHEL 9 | cryostat/cryostat-agent-init-rhel9:0.5.1-1 | RHSA-2025:8265 |
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.516.2.1756902453-3.el8 | RHSA-2025:15813 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.516.2.1756902120-3.el8 | RHSA-2025:15815 |
| OCP-Tools-4.14-RHEL-8 | jenkins-0:2.516.2.1757087588-3.el8 | RHSA-2025:15816 |
| OCP-Tools-4.15-RHEL-8 | jenkins-0:2.516.2.1756738247-3.el8 | RHSA-2025:15817 |
| OCP-Tools-4.16-RHEL-9 | jenkins-0:2.516.2.1756733848-3.el9 | RHSA-2025:15811 |
| OCP-Tools-4.17-RHEL-9 | jenkins-0:2.516.2.1756732303-3.el9 | RHSA-2025:15814 |
| OCP-Tools-4.18-RHEL-9 | jenkins-0:2.516.2.1756731431-3.el9 | RHSA-2025:15810 |
Frequently Asked Questions
Is CVE-2025-48734 in your dependencies?
Find it across Maven, including transitive dependencies.