Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2020-35728 — jackson-databind

HIGHFix: FasterXML/jackson-databind@1ca0388

CVE-2020-35728 is a high-severity (CVSS 8.1) Deserialization of Untrusted Data vulnerability in com.fasterxml.jackson.core:jackson-databind. 3 public exploit references exist, so weaponization risk is real. A fix is available for com.fasterxml.jackson.core:jackson-databind — see the affected versions and patch details below.

Serialization gadget exploit in jackson-databind

Also known asGHSA-5r5r-6hpj-8gg9
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2020-35728.

EPSS Exploitation Probability

via FIRST.org ↗
12.5%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
3.56%19.5%35.4%51.3%40.3%12.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-35728 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕com.fasterxml.jackson.core:jackson-databind

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

FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.fasterxml.jackson.core:jackson-databind≥ 2.0.0&&< 2.9.10.82.9.10.8com.fasterxml.jackson.core:jackson-databind:2.9.10.8

Affected Products

40 products · 66 configurations
OS
debian linuxdebian
1 version
9.0
Application
jackson-databindfasterxml
≥ 2.7.0 && < 2.9.10.8
range
Application
service level managernetapp
all
Application
agile product lifecycle managementoracle
1 version
9.3.6
Application
application testing suiteoracle
1 version
13.3.0.1
Application
autovueoracle
1 version
21.0.2
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update com.fasterxml.jackson.core:jackson-databind to 2.9.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-35728 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

The following Red Hat Products ship jackson-databind version 2.10.0 or later which is not considered affected by this CVE (see https://medium.com/@cowtowncoder/jackson-2-10-safe-default-typing-2d018f0ce2ba) * JBoss Data Grid 7 * JBoss Data Grid 8 * Enterprise Application Platform 7 * Red Hat Decision Manager 7 * Red…

Workaround published by Red Hat
The following conditions are needed for an exploit, we recommend avoiding all if possible: * Deserialization from sources you do not control * `enableDefaultTyping()` * `@JsonTypeInfo using `id.CLASS` or `id.MINIMAL_CLASS` * avoid com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool in the classpath
Source: Red Hat security advisory for CVE-2020-35728 (CC BY 4.0)
ProductFixed inAdvisory
OpenShift Logging 5.0openshift-logging/elasticsearch6-rhel8:v5.0.3-1RHSA-2021:1515
Red Hat OpenShift Container Platform 4.6openshift4/ose-logging-elasticsearch6:v4.6.0-202104161407.p0RHSA-2021:1230

Frequently Asked Questions

FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).
O3 Security · Impact-Aware SCA

Is CVE-2020-35728 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2020-35728: jackson-databind — Fixed in 2.9.10.8