# CVE-2026-58307: Memory corruption in Escargot

> An out-of-bounds read in the Escargot JavaScript engine allows attackers to cause denial of service or read sensitive memory.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-7947-c2xp-c8w5

## What is CVE-2026-58307?

CVE-2026-58307 is a medium-severity memory corruption vulnerability in Samsung Open Source Escargot, published on 9 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Out-of-bounds read, Reachable assertion vulnerability in Samsung Open Source Escargot allows Overread Buffers, Input Data Manipulation.

This issue affects Escargot: before 2dee22f5c7b8bf31cb7252d7731fae8c07f2842c.

Weakness: CWE-617 (Reachable Assertion), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-58307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58307 is a medium-severity memory corruption vulnerability in Samsung Open Source Escargot, published on 9 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-58307 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-58307/ (Markdown: https://insights.sbomify.com/CVE-2026-58307/index.md)
```

## Sources

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

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