Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113602 Overview
CVE-2026-113602 is an input validation bypass vulnerability in the json-smart Java library through version 2.6.0. The flaw allows attackers to evade strict-mode trailing-data checks by inserting a literal 0x1A (SUB) character into JSON payloads. Attackers can append 0x1A followed by malformed content and still pass JSONValue.parseStrict or isValidJsonStrict validation. This creates parser differentials when the same payload is later processed by downstream parsers such as Jackson or Gson, which interpret the content differently. The issue is tracked under CWE-147: Improper Neutralization of Input Terminators.
Critical Impact
Attackers can smuggle data past strict JSON validation, enabling parser differential attacks that bypass security controls relying on json-smart for input sanitization.
Affected Products
- json-smart versions through 2.6.0
- Applications invoking JSONValue.parseStrict
- Applications invoking isValidJsonStrict for validation
Discovery Timeline
- 2026-10-20 - CVE-2026-113602 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113602
Vulnerability Analysis
The vulnerability resides in json-smart's strict parsing routines, which are designed to reject any trailing data after a well-formed JSON document. The parser's trailing-data check does not treat the 0x1A (ASCII SUB, Ctrl+Z) character as invalid trailing content. As a result, a payload containing a valid JSON document followed by 0x1A and arbitrary malformed bytes passes parseStrict and isValidJsonStrict without error.
Downstream JSON parsers such as Jackson and Gson do not share this treatment of 0x1A. When the same payload is forwarded to those libraries, the trailing bytes may be interpreted, rejected, or parsed into a different object entirely. This parser differential is the exploitable primitive. Security systems that validate inbound JSON with json-smart and then hand the raw bytes to another parser for business logic can be tricked into accepting content the validator believed to be clean.
Root Cause
The JSONParserBase implementation accepts 0x1A as a terminator-like character in strict mode rather than flagging it as invalid trailing data. The source is available in the JSONParserBase class on GitHub. The behavior is documented in GitHub issue #302 and the VulnCheck advisory.
Attack Vector
The attack vector is network-based and requires no authentication. An attacker submits a crafted JSON body to any application endpoint that validates input with json-smart strict-mode APIs. By appending 0x1A and malformed data after a well-formed JSON object, the attacker bypasses the validation gate. If the downstream consumer uses a different parser, the attacker can smuggle unexpected fields, duplicate keys, or malformed structures past security controls such as schema enforcement, allowlists, or signature verification layers.
No verified public exploit code is available. The vulnerability mechanism is described in prose in the referenced advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113602
Indicators of Compromise
- Inbound HTTP request bodies or message payloads containing a 0x1A byte following a syntactically valid JSON document.
- Divergent parse results between json-smart and downstream parsers (Jackson, Gson) in application logs or error traces.
- Web application firewall or proxy logs showing requests with non-printable control characters in JSON content types.
Detection Strategies
- Inspect raw request bodies at the ingress layer for 0x1A characters inside application/json payloads and flag or reject them.
- Add instrumentation around JSONValue.parseStrict and isValidJsonStrict call sites to log inputs containing control characters outside the standard JSON whitespace set.
- Compare validation results between json-smart and the downstream parser during canary testing to surface parser differentials.
Monitoring Recommendations
- Monitor dependency manifests (pom.xml, build.gradle) across the estate for net.minidev:json-smart at version 2.6.0 or earlier.
- Alert on application errors from Jackson or Gson that reference unexpected trailing tokens following successful upstream validation.
- Track outbound requests from services that transform JSON after json-smart validation to detect anomalous field values that would not survive consistent validation.
How to Mitigate CVE-2026-113602
Immediate Actions Required
- Inventory all applications and services that depend on net.minidev:json-smart and identify instances at version 2.6.0 or earlier.
- Upgrade json-smart to a fixed release once published by the maintainers, tracked under issue #302.
- Add ingress-layer filtering that rejects JSON payloads containing 0x1A or other non-whitespace control characters before they reach the validator.
Patch Information
No fixed version is listed in the NVD record at the time of publication. Monitor the json-smart-v2 GitHub repository and the VulnCheck advisory for release updates. Until a patch is available, apply the workarounds below.
Workarounds
- Pre-validate inbound JSON by scanning raw bytes and rejecting any payload containing 0x1A prior to invoking json-smart.
- Standardize on a single JSON parser across validation and business logic to eliminate parser differential conditions.
- Re-parse the output of json-smart with the downstream parser and compare normalized results before trusting the input.
# Configuration example
# Example byte-level pre-check (Java pseudocode) to reject payloads containing 0x1A
# before invoking JSONValue.parseStrict
for (byte b : requestBody) {
if (b == 0x1A) {
throw new BadRequestException("Invalid control character in JSON payload");
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

