Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 24 Jun 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apple
Apple m1 Pro |
|
| Vendors & Products |
Apple
Apple m1 Pro |
Wed, 24 Jun 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Apple M1 GPU Register Leakage Enables Secret Recovery Across Sandboxed Apps |
Wed, 24 Jun 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Apple M1 GPU Register Leakage Enables Secret Recovery Across Sandboxed Apps |
Wed, 24 Jun 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-200 | |
| Metrics |
cvssV3_1
|
Wed, 24 Jun 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-06-24T16:05:51.795Z
Reserved: 2026-05-28T00:00:00.000Z
Link: CVE-2026-49269
Updated: 2026-06-24T16:05:35.315Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-24T20:41:18Z