Cyber Resilience

CVE-2023-26819

Cjson Project Cjson 1.7.15

Public PoC
Published
19 April 2025
Modified
03 November 2025
CVSS Score v3.1 2.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0022 13th percentile
Risk Priority 26 floored blend · peak EPSS

Summary

CVE-2023-26819 is a low-severity Expected Behavior Violation (CWE-440) vulnerability in Cjson Project Cjson. Its CVSS base score is 2.9 (Low).

Operationally, ranked at the 13th percentile by exploit likelihood (below the median); 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 SA-11 (Developer Testing and Evaluation) and SI-6 (Security and Privacy Function Verification) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

cJSON 1.7.15 might allow a denial of service via a crafted JSON document such as {"a": true, "b": [ null,9999999999999999999999999999999999999999999999912345678901234567]}.

CWE(s)
CWE-440

Related Threats

CVEs Like This One

CVE-2024-31755Same product: Cjson Project Cjson
CVE-2023-53154Same product: Cjson Project Cjson
CVE-2025-46712Shared CWE-440
CVE-2024-7246Shared CWE-440
CVE-2025-27094Shared CWE-440
CVE-2026-8806Shared CWE-440
CVE-2026-42752Shared CWE-440
CVE-2025-52953Shared CWE-440
CVE-2023-32732Shared CWE-440
CVE-2025-32728Shared CWE-440

Affected Assets

cjson project
cjson
1.7.15

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly checks whether implemented functions match their specifications.

SI-6 Security and Privacy Function Verification good match

Security function verification confirms that functions operate according to their defined expected behavior.

SA-17 Developer Security and Privacy Architecture and Design partial match

Requiring a documented security architecture and design reduces the chance that implementation deviates from intended behavior.

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.

PR.PS-06 full match
prevents

Secure SDLC practices directly enforce specification compliance and catch expected-behavior violations during development.

ID.IM-02 partial match
prevents

Security testing and exercises help discover behavior deviations before deployment.

ID.RA-01 partial match
prevents

Vulnerability identification can surface spec-violating flaws, while eliminating the weakness reduces some vulnerability backlog.

PR.PS-02 partial match
prevents

Routine software maintenance and patching can remediate discovered specification violations.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance validates that functions behave as specified.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates verification against specifications, directly reducing expected-behavior violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly define expected behavior that must be met.

A.8.28 Secure coding partial match
prevents

Secure coding practices enforce adherence to functional specifications during implementation.

A.8.32 Change management partial match
finds

Change management can catch specification deviations introduced by modifications.

A.5.37 Documented operating procedures none match
none

Documented operating procedures reduce the chance that functions deviate from intended behavior.

References