Quick answers
- Is CVE-2026-37736 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37736 being exploited in the wild.
- How severe is CVE-2026-37736?
- High severity, with a CVSS score of 7.5, published 28 August 2026.
- Which products and versions are affected?
- OWASP Json-Sanitizer 1.2.2, 1.2.3, 1.2.4-SNAPSHOT.
- Is there a fix for CVE-2026-37736?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-37736 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-37736?
- Check whether you run OWASP Json-Sanitizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the JsonSanitizer.sanitize() method's internal nesting depth tracking logic. When processing JSON with nesting depth exceeding the default maximum (64 levels), the library performs an out-of-bounds array access, throwing an unhandled ArrayIndexOutOfBoundsException. The attack requires only network-reachable input to the sanitize() function with no authentication required. An attacker can achieve denial of service by causing the application to crash. The issue affects versions 1.2.2, 1.2.3, and 1.2.4-SNAPSHOT, and a fix involves adding strict nesting depth validation before array access.
Affected products
- OWASP json-sanitizer 1.2.2, 1.2.3, 1.2.4-SNAPSHOT
Timeline
- 2026-01-26: disclosed: Vulnerability reported via GitHub issue #35
- 2026-08-28: advisory: CVE-2026-37736 published