The Json Parser Project maintains a single, focused JSON-parsing utility library whose vulnerability footprint reflects the parsing and data-validation demands inherent to structured-data processing. This niche component may be widely embedded across applications and tools, making individual disclosures relevant to a broader downstream surface than the vendor's direct product count suggests. Current exploitation activity, severity distribution, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Json Parser Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-32285HIGH 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 servi | Mar 26, 2026 | 7.5 | 29 | NO | NO |
CVE-2023-23088CRITICAL Buffer OverFlow Vulnerability in Barenboim json-parser master and v1.1.0 fixed in v1.1.1 allows an attacker to execute arbitrary code via the json_value_parse function. | Feb 3, 2023 | 9.8 | 29 | NO | NO |
CVE-2020-35381HIGH jsonparser 1.0.0 allows attackers to cause a denial of service (panic: runtime error: slice bounds out of range) via a GET call. | Dec 15, 2020 | 7.5 | 25 | NO | NO |
CVE-2020-10675HIGH The Library API in buger jsonparser through 2019-12-04 allows attackers to cause a denial of service (infinite loop) via a Delete call. | Mar 19, 2020 | 7.5 | 22 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Json Parser Project.
Media articles that mention a CVE ID that affects a product developed by Json Parser Project — matched by CVE ID, not by vendor name.