Cyber Resilience

CVE-2025-15535

Memory Safety

Published
18 January 2026
Modified
15 April 2026
CVSS Score v4 4.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0012 2th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-15535 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability. Its CVSS base score is 4.8 (Medium).

Operationally, ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A security flaw has been discovered in nicbarker clay up to 0.14. This affects the function Clay__MeasureTextCached in the library clay.h. The manipulation results in null pointer dereference. The attack is only possible with local access. The exploit has been…

more

released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-1416Shared CWE-404, CWE-476
CVE-2026-1417Shared CWE-404, CWE-476
CVE-2026-1976Shared CWE-404, CWE-476
CVE-2024-12660Shared CWE-404, CWE-476
CVE-2026-8782Shared CWE-404, CWE-476
CVE-2024-12659Shared CWE-404, CWE-476
CVE-2025-5867Shared CWE-404, CWE-476
CVE-2025-11550Shared CWE-404, CWE-476
CVE-2025-1877Shared CWE-404, CWE-476
CVE-2025-9384Shared CWE-404, CWE-476

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-16 Memory Protection
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Enforces validation of all inputs to Clay__MeasureTextCached to reject or safely handle null/invalid pointers before dereference occurs.

prevent

Applies memory-protection mechanisms that detect and block null-pointer dereference attempts in the clay.h library at runtime.

prevent

Requires prompt application of patches or workarounds once the reported null-dereference flaw in clay up to 0.14 is fixed by the maintainer.

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 mostly match
prevents

Secure SDLC practices directly include coding standards for correct resource allocation and release.

DE.CM-09 partial match
prevents

Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.

ID.AM-08 partial match
prevents

Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.

PR.IR-04 partial match
prevents

Capacity management helps surface leaks from unreleased resources but does not prevent the coding flaw.

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.

detects

Security testing can detect NULL dereference defects before release.

prevents

Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.

prevents

Secure SDLC mandates defensive coding practices that can prevent NULL dereferences.

prevents

Application security requirements can specify input validation and pointer-safety rules.

prevents

Secure architecture principles encourage defensive design that avoids unsafe pointer use.

prevents

Secure coding standards directly require NULL-pointer checks and safe dereference patterns.

References