# CVE-2026-88389: Null dereference in n/a

> Crafted input triggers a NULL pointer dereference in the Espruino lexer, causing memory corruption and denial of service in release builds.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-pp3g-9mvp-c3vm

## What is CVE-2026-88389?

CVE-2026-88389 is a medium-severity vulnerability in n/a, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Espruino 2v29 (commit bffc6d0) contains a NULL pointer dereference vulnerability in jslGetRawString() in src/jslex.c. Crafted raw/binary string input can cause the lexer to pass a NULL iterator target to jsvLockAgain(). In RELEASE/NO_ASSERT builds, the missing assertion guard allows a write through the NULL pointer, resulting in memory corruption and application termination or denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-88389?


## How do I fix CVE-2026-88389?

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

## Is CVE-2026-88389 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88389 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88389 and fix it if it is affected.

What it is: CVE-2026-88389 is a medium-severity vulnerability in n/a, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88389 exists.

Affected product: n/a. 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-2026-88389/ (Markdown: https://insights.sbomify.com/CVE-2026-88389/index.md)
```

## Sources

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

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