Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77310 medium CVSS 5.3

SSRF (Server-Side Request Forgery) in com.fasterxml.jackson.core:jackson-databind (CVE-2026-77310)

Summary

SSRF in com.fasterxml.jackson.core:jackson-databind (CVE-2026-77310). Risk of unauthorized operations or information disclosure. Exploitable via java.net.InetSocketAddress. Mitigation: upgrade to 2.22.1 or later.

Original description

The description as published by the source.

Summary

CVE-2026-54514 (GHSA-hgj6-7826-r7m5) fixed an eager-DNS-resolution / SSRF issue in jackson-databind's deserialization of java.net.InetSocketAddress by switching to InetSocketAddress.createUnresolved(...) (PR #5951, commit 1f5a1037, released in 2.18.8 / 2.21.4 / 3.1.4). That fix did not cover the sibling java.net.InetAddress branch in the very same FromStringDeserializer.Std._deserialize() switch statement, which still calls InetAddress.getByName(value) and therefore performs an eager forward DNS lookup on attacker-controlled input at deserialization time. The fix is incomplete: the same vulnerability class remains reachable through InetAddress.

Details

File: src/main/java/com/fasterxml/jackson/databind/deser/std/FromStringDeserializer.java

Sibling cases in the same switch:

  • Line 357-358 (UNFIXED):
    case STD_INET_ADDRESS:
    return InetAddress.getByName(value); // eager forward DNS lookup
  • Line 359-381 + helper at 494-496 (FIXED by PR #5951):
    protected InetSocketAddress _inetSocketAddress(String host, int port) {
    // 05-May-2026, tatu: [databind#5951] Prevent DNS lookup:
    return InetSocketAddress.createUnresolved(host, port); // no DNS
    }

InetAddress is a registered standard string-like scalar type (FromStringDeserializer.types() line 73; findDeserializer() maps it to STD_INET_ADDRESS at line 119-120). Any value deserialized into an InetAddress-typed target — a plain POJO field, a polymorphic subtype, or a…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77310 has been found in com.fasterxml.jackson.core:jackson-databind.
Attackers can target a specific entry point like java.net.InetSocketAddress over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade com.fasterxml.jackson.core:jackson-databind to 2.22.1 or later.
If unsure, ask your IT team or search "com.fasterxml.jackson.core:jackson-databind CVE-2026-77310" on the vendor's site.

CVE-2026-77310 (com.fasterxml.jackson.core:jackson-databind) — CWE-918 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: java.net.InetSocketAddress / java.net.InetAddress / InetAddress / InetAddress.getByName
Patched: 2.22.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in com.fasterxml.jackson.core:jackson-databind. Attackers reach the vulnerable code path via java.net.InetSocketAddress without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of com.fasterxml.jackson.core:jackson-databind. Attack surface: java.net.InetSocketAddress / java.net.InetAddress / InetAddress / InetAddress.getByName.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.22.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.fasterxml.jackson.core:jackson-databind を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.fasterxml.jackson.core:jackson-databind to 2.22.1

    ステージング環境で 2.22.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.fasterxml.jackson.core:jackson-databind
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.22.1"}]}]
maven tools.jackson.core:jackson-databind
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details