CVE-2026-68498
waiting for further signalsZero needs more public information before it can validate it.GHSA-649p-m576-vr99 ↗EUVD-2026-103177 ↗
description
Jackson-core versions starting at 2.16.0 in the com.fasterxml.jackson.core line and 3.0.0 in the tools.jackson.core line can consume excessive memory when parsing an untrusted JSON object with an oversized property name from character-based input. An unauthenticated attacker may exhaust heap memory and disrupt the application when it accepts JSON through a String, Reader, or char[] source.
mitigation
Upgrade com.fasterxml.jackson.core:jackson-core to 2.18.10, 2.21.6, or 2.22.2, or upgrade tools.jackson.core:jackson-core to 3.1.6 or 3.2.2. Until upgraded, avoid parsing untrusted JSON from character-based sources and use raw UTF-8 byte input where practical.
fixed in 2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-16 21:11Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-68498
{ "etk_id": "ETK-2026-1824", "cve_id": "CVE-2026-68498", "display_id": "CVE-2026-68498", "ghsa_id": "GHSA-649p-m576-vr99", "euvd_id": "EUVD-2026-103177", "status": "published", "anchor_state": "anchored", "title": "Jackson-core resource exhaustion through oversized JSON field names", "summary": "Jackson-core versions starting at 2.16.0 in the com.fasterxml.jackson.core line and 3.0.0 in the tools.jackson.core line can consume excessive memory when parsing an untrusted JSON object with an oversized property name from character-based input. An unauthenticated attacker may exhaust heap memory and disrupt the application when it accepts JSON through a String, Reader, or char[] source.", "mitigation": "Upgrade com.fasterxml.jackson.core:jackson-core to 2.18.10, 2.21.6, or 2.22.2, or upgrade tools.jackson.core:jackson-core to 3.1.6 or 3.2.2. Until upgraded, avoid parsing untrusted JSON from character-based sources and use raw UTF-8 byte input where practical.", "vendor": "FasterXML", "product": "jackson-core", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 2.16.0, <= 2.18.9" ], "ecosystem": "maven", "fixed_versions": [ "2.18.10" ], "package_name": "com.fasterxml.jackson.core:jackson-core", "purl": "pkg:maven/com.fasterxml.jackson.core/jackson-core" }, { "affected_notes": [], "affected_ranges": [ ">= 2.19.0, <= 2.21.5" ], "ecosystem": "maven", "fixed_versions": [ "2.21.6" ], "package_name": "com.fasterxml.jackson.core:jackson-core", "purl": "pkg:maven/com.fasterxml.jackson.core/jackson-core" }, { "affected_notes": [], "affected_ranges": [ ">= 2.22.0, <= 2.22.1" ], "ecosystem": "maven", "fixed_versions": [ "2.22.2" ], "package_name": "com.fasterxml.jackson.core:jackson-core", "purl": "pkg:maven/com.fasterxml.jackson.core/jackson-core" }, { "affected_notes": [], "affected_ranges": [ ">= 3.0.0, <= 3.1.5" ], "ecosystem": "maven", "fixed_versions": [ "3.1.6" ], "package_name": "tools.jackson.core:jackson-core", "purl": "pkg:maven/tools.jackson.core/jackson-core" }, { "affected_notes": [], "affected_ranges": [ ">= 3.2.0, <= 3.2.1" ], "ecosystem": "maven", "fixed_versions": [ "3.2.2" ], "package_name": "tools.jackson.core:jackson-core", "purl": "pkg:maven/tools.jackson.core/jackson-core" } ], "cwes": [ 400 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "epss_score": 0.0091, "epss_percentile": 0.5942, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 21.999571666666668, "t0_at": "2026-10-16T21:11:03.551000+00:00", "signals": { "trigger_signal": { "at": "2026-10-16T21:11:03.551000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-16T21:11:03.551000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-68498" } } }
published 2026-10-16 23:59Z
last change 2026-10-21 05:31Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.