Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-29062: CWE-770: Allocation of Resources Without Limits or Throttling in FasterXML jackson-core

0
High
VulnerabilityCVE-2026-29062cvecve-2026-29062cwe-770
Published: Fri Mar 06 2026 (03/06/2026, 07:14:25 UTC)
Source: CVE Database V5
Vendor/Project: FasterXML
Product: jackson-core

Description

jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. From version 3.0.0 to before version 3.1.0, the UTF8DataInputJsonParser, which is used when parsing from a java.io.DataInput source, bypasses the maxNestingDepth constraint (default: 500) defined in StreamReadConstraints. A similar issue was found in ReaderBasedJsonParser. This allows a user to supply a JSON document with excessive nesting, which can cause a StackOverflowError when the structure is processed, leading to a Denial of Service (DoS). This issue has been patched in version 3.1.0.

AI-Powered Analysis

AILast updated: 03/06/2026, 07:45:53 UTC

Technical Analysis

CVE-2026-29062 is a vulnerability in the jackson-core library, specifically affecting versions from 3.0.0 up to but not including 3.1.0. Jackson-core is a widely used Java library for processing JSON data, providing core low-level streaming parser and generator abstractions. The vulnerability arises because the UTF8DataInputJsonParser, which parses JSON from a java.io.DataInput source, bypasses the maxNestingDepth constraint defined in StreamReadConstraints. This constraint, set by default to 500, is intended to prevent excessively nested JSON structures that could cause resource exhaustion. A similar bypass exists in ReaderBasedJsonParser. By supplying a JSON document with excessive nesting, an attacker can cause the parser to exceed the stack depth, resulting in a StackOverflowError. This error leads to a denial of service (DoS) condition as the application processing the JSON input crashes or becomes unresponsive. The flaw is categorized under CWE-770, which relates to allocation of resources without proper limits or throttling. The vulnerability requires no authentication or user interaction and can be exploited remotely by sending crafted JSON data. The issue was addressed and patched in jackson-core version 3.1.0. No public exploits have been reported yet, but the high CVSS 8.7 score reflects the significant risk posed by this vulnerability.

Potential Impact

The primary impact of CVE-2026-29062 is denial of service (DoS) through application crashes caused by StackOverflowError when processing maliciously crafted JSON input with excessive nesting. Organizations using jackson-core versions 3.0.0 to before 3.1.0 in their Java applications are at risk. This can affect web services, APIs, and backend systems that parse JSON data from untrusted or external sources. The DoS can disrupt service availability, degrade user experience, and potentially cause cascading failures in dependent systems. Since jackson-core is widely adopted in enterprise Java applications globally, the scope of affected systems is broad. Attackers do not require authentication or user interaction, making exploitation easier. Although no known exploits are currently in the wild, the vulnerability’s presence in a fundamental JSON parsing library makes it a critical risk for many organizations, especially those exposing JSON interfaces to the internet or processing third-party data.

Mitigation Recommendations

To mitigate CVE-2026-29062, organizations should upgrade jackson-core to version 3.1.0 or later, where the maxNestingDepth constraint bypass is fixed. For environments where immediate upgrade is not feasible, implement input validation to reject JSON documents with excessive nesting before parsing. Employ Web Application Firewalls (WAFs) or API gateways to detect and block suspiciously nested JSON payloads. Monitor application logs for StackOverflowError or abnormal crashes related to JSON parsing. Consider sandboxing or isolating JSON processing components to limit impact of potential DoS. Regularly audit dependencies and apply security patches promptly. Educate developers on secure JSON handling practices, including setting explicit limits on JSON complexity and nesting depth. Finally, incorporate fuzz testing and stress testing of JSON parsers to identify similar resource exhaustion issues proactively.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-03T17:50:11.245Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69aa82b7c48b3f10ff296e55

Added to database: 3/6/2026, 7:31:03 AM

Last enriched: 3/6/2026, 7:45:53 AM

Last updated: 3/6/2026, 9:29:13 PM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses