# CVE-2026-86315: Integer overflow in Escargot

> An attacker can crash the host process or potentially execute code by supplying crafted JavaScript that triggers an out-of-bounds write via integer truncation in the Escargot engine.

- **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:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-xh23-cpx8-xqgm

## What is CVE-2026-86315?

CVE-2026-86315 is a medium-severity vulnerability in Samsung Opensource Escargot, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds write caused by numeric truncation  Samsung Open Source Escargot on Linux x86-64 allows an attacker who can supply JavaScript for execution to corrupt native memory and crash the host process via a crafted class definition whose instance initialization entry count exceeds UINT16_MAX.

This issue affects Escargot: 5dc93606abd42b859045add05d704a038e197359.

Weakness: CWE-197 (Numeric Truncation Error)

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


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

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

## Is CVE-2026-86315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86315 is a medium-severity vulnerability in Samsung Opensource Escargot, published on 7 Sep 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-2026-86315 in the wild and no public exploit code.

Affected product: Samsung Opensource Escargot. 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-86315/ (Markdown: https://insights.sbomify.com/CVE-2026-86315/index.md)
```

## Sources

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

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