CVE-2026-113602

What it is

json-smart through 2.6.0 contains an input validation bypass vulnerability that allows attackers to evade strict-mode trailing-data checks by inserting a literal 0x1A character. Attackers can append 0x1A and malformed content to pass JSONValue.parseStrict or isValidJsonStrict validation, creating parser differentials with downstream parsers like Jackson or Gson.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2026-10-20 11:48 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-10-20 16:17 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-10-20 20:06 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 6.9 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2026-10-20 16:17 UTC

Last modified

2026-10-20 20:06 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-147

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 6.9

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-113602.md and follow it. Check whether this project is affected by CVE-2026-113602. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge