# CVE-2026-129543: Memory corruption in Starfish

> Malicious web content can trigger type confusion in Samsung Starfish WebGL bufferData, corrupting memory in apps using it.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`bufferData()`)
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-w34m-j345-gr8w

## What is CVE-2026-129543?

CVE-2026-129543 is a medium-severity memory corruption vulnerability in Samsung Open Source Starfish, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, 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 Starfish allows Input Data Manipulation.

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

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

An affected version is only exploitable if your software calls bufferData(). Many projects that include it are not exposed.


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

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

## Is CVE-2026-129543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129543 is a medium-severity memory corruption vulnerability in Samsung Open Source Starfish, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-129543 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls bufferData(). Many projects that include it are not exposed.

Affected product: Samsung Open Source Starfish. 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.
   If an affected version is present, also search the code for calls to bufferData() and report whether any exist.
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-129543/ (Markdown: https://insights.sbomify.com/CVE-2026-129543/index.md)
```

## Sources

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

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