Polymorphic deserialization of malicious object in jackson-databind
Published 15 May 2020 · Updated 7 Aug 2026
Is your project on an affected com.fasterxml.jackson.core:jackson-databind?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.9.0 <2.9.10
- Fixed in
- 2.9.10
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.9.10 -DforceVersion=trueDetails
A flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as enableDefaultTyping() or when @JsonTypeInfo is using Id.CLASS or Id.MINIMAL_CLASS or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.
Is GHSA-qmqc-x3r4-6v39 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected com.fasterxml.jackson.core:jackson-databind, and gives you the command that fixes it.
More advisories for com.fasterxml.jackson.core:jackson-databind
- HighCVE-2026-91777jackson-databind quadratic forward-reference completion · 30 Sept 2026
- HighCVE-2026-91776jackson-databind retains every unknown raw type ID · 30 Sept 2026
- MediumCVE-2026-83557jackson-databind: Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist) · 28 Sept 2026
- HighCVE-2026-68497jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS · 28 Sept 2026
- MediumCVE-2026-19032jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution · 28 Sept 2026
- MediumCVE-2026-77310jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization · 28 Sept 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-14893
- Linkgithub.com/FasterXML/jackson-databind/issues/2469
- Linkgithub.com/FasterXML/jackson-databind/commit/998efd708284778f29d83d7962a9bd935c228317
- Linkaccess.redhat.com/errata/RHSA-2020:0729
- Linkbugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14893
- Linklists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E
- Linklists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E
- Linksecurity.netapp.com/advisory/ntap-20200327-0006
- Linkwww.oracle.com/security-alerts/cpujul2020.html
- Linkwww.oracle.com/security-alerts/cpuoct2020.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.