# CVE-2026-95115: Memory corruption in n/a

> A remote attacker can cause a denial of service via a buffer overflow in the libwebsockets JSON parser.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** BELL-CVE-2026-95115, DEBIAN-CVE-2026-95115, GHSA-9f4q-6c78-chwx, UBUNTU-CVE-2026-95115

## What is CVE-2026-95115?

CVE-2026-95115 is a high-severity memory corruption vulnerability in n/a, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in libwebsockets main 106d542c allows a remote attacker to cause a denial of service via the LEJP JSON parser

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-95115 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95115 is a high-severity memory corruption vulnerability in n/a, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95115 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-95115/ (Markdown: https://insights.sbomify.com/CVE-2026-95115/index.md)
```

## Sources

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

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