Security readout for executives and security teams
Plain-English summary
Jackson-core 3.0.x can fail to enforce JSON nesting limits in specific parser paths. An attacker who can submit deeply nested JSON may trigger a StackOverflowError and cause denial of service. The issue is patched in jackson-core 3.1.0.
Executive priority
Treat as high priority for exposed Java services because the patch is available and exploitation could cause service outages without authentication. Focus first on internet-facing APIs and products using jackson-core 3.0.x.
Technical view
Versions 3.0.0 before 3.1.0 bypass StreamReadConstraints maxNestingDepth in UTF8DataInputJsonParser for java.io.DataInput sources. The description also notes a similar ReaderBasedJsonParser issue. Excessive nesting can exhaust stack during processing, causing DoS. CVSS v4 score is 8.7.
Likely exposure
Likely exposure is Java applications or dependencies using jackson-core 3.0.x to parse untrusted JSON, especially network APIs. Exposure is strongest where DataInput or affected reader-based parser paths are used. The supplied sources do not show jackson-core 2.x as affected.
Exploitation context
No KEV listing is provided, and the source bundle does not cite active exploitation. The CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction. Practical impact depends on exposed JSON parsing paths and service resilience.
Researcher notes
The core issue is constraint bypass, not arbitrary code execution. Validate exposure by version and parser path, then assess whether untrusted input reaches affected Jackson parsing. Evidence is incomplete for exploitation in the wild, so avoid claiming active attacks.
Mitigation direction
- Upgrade jackson-core to version 3.1.0 or later.
- Inventory direct and transitive jackson-core 3.0.x dependencies.
- Prioritize internet-facing services that parse untrusted JSON.
- Check FasterXML and downstream vendor guidance for platform-specific updates.
- Use service-level request size and depth controls where available.
Validation and detection
- Confirm dependency resolution does not include jackson-core 3.0.x.
- Review API paths accepting untrusted JSON input.
- Identify code paths using java.io.DataInput or reader-based Jackson parsers.
- Verify deployed artifacts include jackson-core 3.1.0 or later.
- Check monitoring for StackOverflowError or JSON parsing DoS symptoms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1284: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-29062 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADPVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-06T08:01:16.445Z: Reported to Red Hat.
- 2026-03-06T07:14:25.059Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/FasterXML/jackson-core/security/advisories/GHSA-6v53-7c9g-w56rCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/FasterXML/jackson-core/pull/1554CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FasterXML/jackson-core/commit/8b25fd67f20583e75fb09564ce1eaab06cd5a902CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-29062CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2445135CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29062.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.