GHSA-gww7-p5w4-wrfv is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in com.fasterxml.jackson.core:jackson-databind. O3 Security confirms whether GHSA-gww7-p5w4-wrfv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Deserialization of Untrusted Data in jackson-databind
Real-World Exposure
com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databindReal-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
FasterXML jackson-databind 2.x before 2.6.7.4, 2.7.x before 2.7.9.7, 2.8.x before 2.8.11.5, and 2.9.x before 2.9.10.2 lacks certain net.sf.ehcache blocking.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.fasterxml.jackson.core:jackson-databind | ≥ 2.0.0&&< 2.6.7.4 | 2.6.7.4 |
| ☕Maven | com.fasterxml.jackson.core:jackson-databind | ≥ 2.7.0&&< 2.7.9.7 | 2.7.9.7 |
| ☕Maven | com.fasterxml.jackson.core:jackson-databind | ≥ 2.8.0&&< 2.8.11.5 | 2.8.11.5 |
| ☕Maven | com.fasterxml.jackson.core:jackson-databind | ≥ 2.9.0&&< 2.9.10.2 | 2.9.10.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.fasterxml.jackson.core:jackson-databind. 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 com.fasterxml.jackson.core:jackson-databind to 2.6.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gww7-p5w4-wrfv 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-gww7-p5w4-wrfv 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-gww7-p5w4-wrfv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
While OpenShift Container Platform's elasticsearch plugins do ship the vulnerable component, it doesn't do any of the unsafe things described in https://access.redhat.com/solutions/3279231. We may update the jackson-databind dependency in a future release.
Frequently Asked Questions
Is GHSA-gww7-p5w4-wrfv in your dependencies?
O3 detects GHSA-gww7-p5w4-wrfv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.