jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)
Published 23 Jun 2026 · Updated 10 Nov 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 packages
- Affected
- >=2.0.0 <2.18.8
- Fixed in
- 2.18.8
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.18.8 -DforceVersion=true- Affected
- >=2.19.0 <2.21.4
- Fixed in
- 2.21.4
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.21.4 -DforceVersion=true- Affected
- >=3.0.0 <3.1.4
- Fixed in
- 3.1.4
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=trueDetails
Summary
JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect.
Impact
An attacker controlling JSON deserialized into an InetSocketAddress-bearing type can force outbound DNS lookups for attacker-chosen hostnames at deserialization time (SSRF / DNS-based out-of-band interaction / internal-resolver probing), purely from binding.
Affected / Patched (verified via git tag --contains on 1f5a103)
- 2.18 line:
>= 2.18.0, < 2.18.8-> fixed in 2.18.8 - 2.19-2.21 line:
>= 2.19.0, < 2.21.4-> fixed in 2.21.4 - 3.x line:
>= 3.0.0, < 3.1.4-> fixed in 3.1.4
Severity / CWE
Maintainer: minor. Reporter: LOW. CWE-918 (SSRF).
Upstream fix
FasterXML/jackson-databind#5951 ("Improve InetSocketAddress deserialization"). Released 2026-06-04 in 2.18.8 / 2.21.4 / 3.1.4.
Credits
Omkhar Arasaratnam (@omkhar) - finder.
Is GHSA-hgj6-7826-r7m5 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
- Linkgithub.com/FasterXML/jackson-databind/security/advisories/GHSA-hgj6-7826-r7m5
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-54514
- Linkgithub.com/FasterXML/jackson-databind/pull/5951
- Linkgithub.com/FasterXML/jackson-databind/commit/1f5a1037b1e9e05920e755cb35f198bcd46667e4
- Packagegithub.com/FasterXML/jackson-databind
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.