CVE-2026-32285
Jsonparser Project Jsonparser ≤ 1.1.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-32285 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Jsonparser Project Jsonparser. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-32285 is a vulnerability in the Delete function of the jsonparser library (github.com/buger/jsonparser) for Go. It stems from a failure to properly validate offsets when processing malformed JSON input, resulting in a negative slice index that triggers a runtime panic and enables a denial-of-service condition. The issue is classified under CWE-129 (Improper Validation of Array Index) and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), highlighting its high availability impact.
Unauthenticated remote attackers can exploit this vulnerability by supplying specially crafted malformed JSON input to applications using the affected jsonparser Delete function. Exploitation requires low complexity and no user interaction, allowing network-based denial of service through induced runtime panics that crash the application.
Mitigation details are available in related advisories, including the Go vulnerability database entry GO-2026-4514 (pkg.go.dev/vuln/GO-2026-4514), the Golang vulndb issue (github.com/golang/vulndb/issues/4514), the jsonparser library issue (github.com/buger/jsonparser/issues/275), and security research from securityinfinity.com/research/buger-jsonparser-negative-slice-panic-dos-2026. Security practitioners should consult these for patch information and update guidance.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16345
Vulnerability Data
The Delete function fails to properly validate offsets when processing malformed JSON input. This can lead to a negative slice index and a runtime panic, allowing a denial of service attack.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.2V2.1.1V2.2.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.
Vulnerability identification processes can discover missing index validation via scanning or reviews.
Patching and replacement can remediate instances of the weakness after discovery.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.
Application security requirements include validation of untrusted input used for indexing or addressing memory structures.
Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.
Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.