How severe is GHSA-6phf-73q6-gh87?

GHSA-6phf-73q6-gh87 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6phf-73q6-gh87?

GHSA-6phf-73q6-gh87 affects the following packages: commons-beanutils:commons-beanutils (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6phf-73q6-gh87?

Update commons-beanutils:commons-beanutils to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6phf-73q6-gh87 is resolved across your whole dependency graph.

How do I detect GHSA-6phf-73q6-gh87 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-beanutils:commons-beanutils. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6phf-73q6-gh87 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-6phf-73q6-gh87?

O3 pinpoints whether GHSA-6phf-73q6-gh87 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6phf-73q6-gh87 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6phf-73q6-gh87 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 type of vulnerability is GHSA-6phf-73q6-gh87?

GHSA-6phf-73q6-gh87 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-6phf-73q6-gh87 published, and has it been updated?

GHSA-6phf-73q6-gh87 was published on June 15, 2020 and was last updated on February 4, 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

HIGH severity

GHSA-6phf-73q6-gh87

HIGH

GHSA-6phf-73q6-gh87 is a high-severity (CVSS 7.3) Deserialization of Untrusted Data vulnerability in commons-beanutils:commons-beanutils. O3 Security confirms whether GHSA-6phf-73q6-gh87 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Insecure Deserialization in Apache Commons Beanutils

Also known asCVE-2019-10086

Published

Jun 15, 2020

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

☕commons-beanutils:commons-beanutils

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

In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-beanutils:commons-beanutils`	all versions	1.9.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-beanutils:commons-beanutils. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update commons-beanutils:commons-beanutils to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6phf-73q6-gh87 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-6phf-73q6-gh87 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6phf-73q6-gh87. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6phf-73q6-gh87 in your dependencies?

O3 detects GHSA-6phf-73q6-gh87 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works