# CVE-2026-58305: Memory corruption in Escargot

> A type confusion vulnerability in the Escargot JavaScript engine allows attackers to manipulate pointers, potentially leading to arbitrary code execution.

- **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-f5pv-4r42-w7j4

## What is CVE-2026-58305?

CVE-2026-58305 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

Access of resource using incompatible type ('type confusion') vulnerability in Samsung Open Source Escargot allows Pointer Manipulation.

This issue affects Escargot: before 779f6bedf58f334dec64b0a51ebb724b4708b84a.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

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

## Is CVE-2026-58305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58305 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-58305 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-58305/ (Markdown: https://insights.sbomify.com/CVE-2026-58305/index.md)
```

## Sources

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

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