jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)
CVE-2026-54514GHSA-hgj6-7826-r7m5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (tools.jackson.core:jackson-databind 3.1.4, 2.21.4; com.fasterxml.jackson.core:jackson-databind 3.1.4, 2.21.4, 2.18.8), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven tools.jackson.core:jackson-databind
- Affected
- >= 2.19.0, < 2.21.4>= 3.0.0, < 3.1.4
- Fixed in
- 2.21.4, 3.1.4
Maven com.fasterxml.jackson.core:jackson-databind
- Affected
- >= 2.0.0, < 2.18.8>= 2.19.0, < 2.21.4>= 3.0.0, < 3.1.4
- Fixed in
- 2.21.4, 2.18.8, 3.1.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hgj6-7826-r7m5 lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=2.0.0 =2.19.0 =3.0.0 =2.19.0 =3.0.0 <3.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-54514: 0.37% estimated exploitation activity in the next 30 days; percentile 30.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-hgj6-7826-r7m5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54514 Advisory: jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF) IDs: CVE-2026-54514, GHSA-hgj6-7826-r7m5 Record: https://patchnext.com/advisories/cve-2026-54514 (revision 1, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: tools.jackson.core:jackson-databind 3.1.4, 2.21.4; com.fasterxml.jackson.core:jackson-databind 3.1.4, 2.21.4, 2.18.8. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven tools.jackson.core:jackson-databind: affected >= 2.19.0, < 2.21.4; >= 3.0.0, < 3.1.4; fixed in 2.21.4, 3.1.4 - Maven com.fasterxml.jackson.core:jackson-databind: affected >= 2.0.0, < 2.18.8; >= 2.19.0, < 2.21.4; >= 3.0.0, < 3.1.4; fixed in 2.21.4, 2.18.8, 3.1.4 ## Suggested inspection (read-only) - Maven tools.jackson.core:jackson-databind: check the installed version with your package manager. - Maven com.fasterxml.jackson.core:jackson-databind: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on tools.jackson.core:jackson-databind, com.fasterxml.jackson.core:jackson-databind. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-hgj6-7826-r7m5 (GitHub-reviewed advisory GHSA-hgj6-7826-r7m5 lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=2.0.0 =2.19.0 =3.0.0 =2.19.0 =3.0.0 <3.1.4) Commands are suggestions: review each one before running it.
Loading voting…