# CVE-2026-92259: Integer overflow in Escargot

> Attackers with write access to the bytecode-cache directory can cause a heap-based buffer overflow and denial of service in Samsung Escargot.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-7xgc-2366-64gq

## What is CVE-2026-92259?

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

### Official description

Integer overflow or wraparound vulnerability in Samsung Opensource Escargot allows attackers with write access to the bytecode-cache directory to cause a heap-based buffer overflow and denial of service via a crafted cache file.

This issue affects Escargot: ac94df78493ee6fede286620d94f724e46b4d238.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-92259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92259 is a medium-severity vulnerability in Samsung Opensource Escargot, published on 15 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-92259 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-92259/ (Markdown: https://insights.sbomify.com/CVE-2026-92259/index.md)
```

## Sources

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

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