CVE-2026-49269

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(high)
EPSS
22.0%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

CVE-2026-49269: Apple M1 GPU residual register information disclosure · GitHub

https://gist.github.com/scndls/9cbe31f2b0b1578eaeb311e601335355

Vendor Advisories for CVE-2026-49269(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 33× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 19:55 UTCEG score recompute
  2. 2026-07-06 19:55 UTCGHSA enrichment
  3. 2026-07-06 19:52 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 06:59 UTCEG score recompute
  6. 2026-07-06 06:59 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 18:34 UTCEG score recompute
  9. 2026-07-05 18:34 UTCGHSA enrichment
  10. 2026-07-05 06:09 UTCEG score recompute
  11. 2026-07-05 06:09 UTCGHSA enrichment
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 17:43 UTCEG score recompute
  14. 2026-07-04 17:43 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 05:18 UTCEG score recompute
  17. 2026-07-04 05:18 UTCGHSA enrichment
  18. 2026-07-03 16:51 UTCEG score recompute
  19. 2026-07-03 16:50 UTCGHSA enrichment
  20. 2026-07-03 04:24 UTCEG score recompute
  21. 2026-07-03 04:24 UTCGHSA enrichment
  22. 2026-07-02 15:59 UTCEG score recompute
  23. 2026-07-02 15:59 UTCGHSA enrichment
  24. 2026-07-02 03:34 UTCEG score recompute
  25. 2026-07-02 03:34 UTCGHSA enrichment
Show 37 more
  1. 2026-07-01 15:09 UTCEG score recompute
  2. 2026-07-01 15:09 UTCGHSA enrichment
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-07-01 02:45 UTCEG score recompute
  5. 2026-07-01 02:45 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 14:20 UTCEG score recompute
  8. 2026-06-30 14:20 UTCGHSA enrichment
  9. 2026-06-30 01:54 UTCEG score recompute
  10. 2026-06-30 01:54 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 13:30 UTCEG score recompute
  14. 2026-06-29 13:30 UTCGHSA enrichment
  15. 2026-06-29 01:05 UTCEG score recompute
  16. 2026-06-29 01:05 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 12:40 UTCEG score recompute
  19. 2026-06-28 12:40 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 00:16 UTCEG score recompute
  23. 2026-06-28 00:15 UTCGHSA enrichment
  24. 2026-06-27 11:49 UTCEG score recompute
  25. 2026-06-27 11:49 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-26 23:24 UTCEG score recompute
  28. 2026-06-26 23:24 UTCGHSA enrichment
  29. 2026-06-26 11:00 UTCEG score recompute
  30. 2026-06-26 11:00 UTCGHSA enrichment
  31. 2026-06-25 19:21 UTCEG score recompute
  32. 2026-06-25 19:21 UTCGHSA enrichment
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 06:56 UTCEG score recompute
  35. 2026-06-25 06:56 UTCGHSA enrichment
  36. 2026-06-24 18:31 UTCEG score recompute
  37. 2026-06-24 18:02 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49269?
CVE-2026-49269 is a high vulnerability published on June 24, 2026. 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…
When was CVE-2026-49269 disclosed?
CVE-2026-49269 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49269 actively exploited?
CVE-2026-49269 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49269?
CVE-2026-49269 has a CVSS v3.1 base score of 8.6 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49269?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49269, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49269

Explore →

Is Your Infrastructure Affected by CVE-2026-49269?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs