CVE-2025-15535VulnerabilityPublished 18 Jan 2026Updated 23 Feb 2026

CVE-2025-15535: nicbarker clay · NULL Pointer Dereference

Affects nicbarker claySource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS: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

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
nicbarkerclay	Affected =0.1 =0.2 =0.3 =0.4 =0.5 =0.6 =0.7 =0.8 =0.9 =0.10 =0.11 =0.12 =0.13 =0.14	Fixed in–
GitHubnicbarker/clay`pkg:github/nicbarker/clay`Other threats	Affected =0.1 =0.2 =0.3 =0.4 =0.5 =0.6 =0.7 =0.8 =0.9 =0.10 =0.11 =0.12 =0.13 =0.14	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should first identify all instances where the nicbarker clay library (versions 0.1 to 0.14) is used, particularly in local or multi-user environments. Until an official patch is released, consider applying the following specific measures: 1) Restrict local access to trusted users only, minimizing the risk of untrusted actors triggering the flaw. 2) Employ application-level sandboxing or containerization to isolate processes using the clay library, limiting the impact of crashes. 3) Monitor logs and system stability for signs of crashes related to Clay__MeasureTextCached to detect exploitation attempts early. 4) If feasible, review and patch the source code locally by adding null pointer checks in the Clay__MeasureTextCached function to prevent dereference. 5) Engage with the project maintainers to encourage timely patch release and track updates. 6) Implement robust local access controls and audit mechanisms to detect unauthorized access. These targeted steps go beyond generic advice by focusing on local access restrictions, code-level hardening, and proactive monitoring tailored to this vulnerability's characteristics.

Description

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 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.

Impact

The primary impact of this vulnerability is denial of service through application or process crashes caused by null pointer dereference. For organizations, this can lead to service interruptions, reduced reliability, and potential operational disruptions if the clay library is used in critical local applications or services. Since exploitation requires local access, the threat is mainly to environments where multiple users share systems or where attackers can gain local foothold, such as development machines, shared servers, or containerized environments. Although the vulnerability does not directly compromise confidentiality or integrity, repeated crashes could be leveraged as part of a larger attack chain to degrade system availability or facilitate privilege escalation attempts. The availability impact could affect development workflows, automated systems, or embedded devices using the vulnerable library. The lack of a patch and public exploit availability increases the urgency for mitigation to prevent opportunistic attacks.

References

Community reviews

Loading reviews…