# CVE-2025-15535: nicbarker clay clay.h Clay__MeasureTextCached null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in the Clay__MeasureTextCached function of the clay library.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-xvvx-g2mg-wqw5

## What is CVE-2025-15535?

CVE-2025-15535 is a medium-severity vulnerability in nicbarker clay, published on 18 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2025-15535?


## How do I fix CVE-2025-15535?

No fix has been published for CVE-2025-15535 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15535 being exploited?

There is no known exploitation of CVE-2025-15535 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15535 and fix it if it is affected.

What it is: CVE-2025-15535 is a medium-severity vulnerability in nicbarker clay, published on 18 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15535 in the wild and no public exploit code.

Affected product: nicbarker clay. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15535/ (Markdown: https://insights.sbomify.com/CVE-2025-15535/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15535
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15535
- OSV: https://osv.dev/vulnerability/CVE-2025-15535

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15535/
Summaries are generated and may contain mistakes; the official description above is the record.