# CVE-2026-49269: Information disclosure in n/a

> A sandboxed app can recover sensitive data from stale GPU registers left by another app on legacy Apple M1 hardware.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-vwgr-66jm-j45f

## What is CVE-2026-49269?

CVE-2026-49269 is a high-severity vulnerability in n/a, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apple M1 GPUs retain register file data between compute shader dispatches from different processes. A sandboxed Metal attacker app can run a GPU reader shader that reads stale register values left by a separate sandboxed victim app. In the proof of concept, GPUVictim.app generates a fresh random 128-bit secret using SecRandomCopyBytes and loads it into GPU registers. GPUAttacker.app, a separate sandboxed app, recovers the exact secret from stale GPU register state. NOTE: The vendor stated that this behavior affects only legacy hardware and has already been addressed at the hardware level in current-generation Apple Silicon.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-49269 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49269 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49269 is a high-severity vulnerability in n/a, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49269 exists.

Affected product: n/a. 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-49269/ (Markdown: https://insights.sbomify.com/CVE-2026-49269/index.md)
```

## Sources

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

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