# CVE-2026-14160: Race condition in Escargot

> A race condition in the Escargot JavaScript engine allows attackers to exploit time-of-check time-of-use flaws, potentially leading to code execution.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-jpx9-q676-jrjx

## What is CVE-2026-14160?

CVE-2026-14160 is a medium-severity vulnerability in Samsung Open Source Escargot, published on 30 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Time-of-check time-of-use (TOCTOU) race condition vulnerability in Samsung Open Source Escargot allows Leveraging Race Conditions.

This issue affects Escargot: bab3a5797557014ce3c2e28419a6310cfba90d0d.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-14160 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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