CVE-2026-77310jackson-databind: Eager DNS resolution (SSRF) still present in InetAddress deserialization (Incomplete fix for CVE-2026-54514)
Updated under an hour ago ()
Does this affect you?
It affects FasterXML com.fasterxml.jackson.core:jackson-databind and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 5.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Weakness (CWE)
- CWE-918
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Aug 25, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
FasterXML com.fasterxml.jackson.core:jackson-databind fasterxml:com.fasterxml.jackson.core_jackson_databind (from the name) | from 2.0.0, < 2.18.9; from 2.19.0, < 2.21.5; from 2.22.0, < 2.22.1 | CNA record |
FasterXML tools.jackson.core:jackson-databind fasterxml:tools.jackson.core_jackson_databind (from the name) | from 3.0.0, < 3.1.5; from 3.2.0, < 3.2.1 | CNA record |
References
- https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-vvgp-rfg2-7rr6x-refsource-confirm
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.