# jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization Advisory record · `GHSA-vvgp-rfg2-7rr6` - **Identifiers:** `GHSA-vvgp-rfg2-7rr6` · `CVE-2026-77310` - **State:** Confirmed - **Severity:** CVSS 5.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html) - **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) - **Published:** 28 Sept 2026 - **Updated:** 28 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 28 Sept 2026, 20:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `com.fasterxml.jackson.core:jackson-databind` (Maven): affected `>=2.0.0, <2.18.9 || >=2.19.0, <2.21.5 || >=2.22.0, <2.22.1`; fixed in `2.18.9`, `2.21.5`, `2.22.1` - `tools.jackson.core:jackson-databind` (Maven): affected `>=3.0.0, <3.1.5 || >=3.2.0, <3.2.1`; fixed in `3.1.5`, `3.2.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Jackson-databind versions 2.0.0 up to 2.18.9, 2.19.0 up to 2.21.5, and 2.22.0 up to 2.22.1, plus tools.jackson.core:jackson-databind 3.0.0 up to 3.1.5 and 3.2.0 up to 3.2.1, are affected. When deserializing into an InetAddress, the library performs a forward DNS lookup on attacker-supplied input, which lets an attacker who can influence the JSON trigger out-of-band DNS requests and probe whether internal hostnames resolve. Upgrade to 2.18.9, 2.21.5, 2.22.1, 3.1.5, or 3.2.1 as applicable; the source does not describe a workaround. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0031, the 24th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vvgp-rfg2-7rr6) ## Sources - [GitHub Advisory Database: GHSA-vvgp-rfg2-7rr6](https://github.com/advisories/GHSA-vvgp-rfg2-7rr6) - [OSV: GHSA-vvgp-rfg2-7rr6](https://osv.dev/vulnerability/GHSA-vvgp-rfg2-7rr6) - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .