Deserialization of Untrusted Data Affecting jackson-databind package, versions <0:2.16.1-4.amzn2023.0.2


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.37% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-JACKSONDATABIND-18061856
  • published21 Jul 2026
  • disclosed23 Jun 2026

Introduced: 23 Jun 2026

CVE-2026-54514  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 jackson-databind to version 0:2.16.1-4.amzn2023.0.2 or higher.
This issue was patched in ALAS2023-2026-1947.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jackson-databind package and not the jackson-databind package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, 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. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

CVSS Base Scores

version 3.1