Researchers discover a cross-origin attack exploiting how modern GPUs compress images to let a malicious website in Chrome or Edge read pixels from another site
https://arstechnica.com/... Dan Goodin / @dangoodin@infosec.exchange : I'm not sure how to think of this new GPU.zip attack. The side channel exists in the GPUs themselves, so it seems fair to think they are vulnerable. — On the other hand, the only (known) way to exploit this side channel is loading iframes into Chrome or Edge, so it also seems reasonable to say these browsers are the things that are vulnerable. … Aida Akl / @AAKL@noc.social : Newly discovered attack lets malicious websites “read the usernames, passwords, and other sensitive visual data displayed by other websites.” #infosec #cybersecurity — It “violates a critical security principle that forms one of the most fundamental security boundaries safeguarding the Internet.” … Bluesky: @blueheronhollow.bsky.social : This is an interesting attack vector. [embedded post] Forums: Hacker News : Sidechannel pixel-stealing attack works in Chromium on all modern GPUs r/technology : GPUs from all major suppliers are vulnerable to new pixel-stealing attack r/hardware : GPUs from all major suppliers are vulnerable to new pixel-stealing attack | Ars Technica r/LinusTechTips : Can someone explain what this means to me. BeauHD / Slashdot : GPUs From All Major Suppliers Are Vulnerable To New Pixel-Stealing Attack Ars OpenForum : GPUs from all major suppliers are vulnerable to new pixel-stealing attack
Context & Ripple Effects
GPU.zip extends a recurring line of hardware-mediated web attacks. Related coverage previously showed a browser side channel that remained viable even with JavaScript blocked, underscoring that browser-level controls alone do not always contain leakage from underlying compute behavior.
The disclosure also sits beside repeated CPU side-channel research, including a power-management attack targeting Intel and AMD systems. Its significance is that a cross-origin boundary can be exposed through the graphics path used by mainstream browsers.
First-order effects
- People who load a malicious page in Chrome or Edge could have sensitive visual content from another site exposed as pixel data when the attack’s conditions are met.
- Chrome and Edge inherit a security problem whose leakage mechanism is in GPU image compression, making the browser’s iframe and rendering paths an immediate mitigation focus.
Second-order effects
- Browser teams may need to reassess how cross-origin content is rendered and isolated, because conventional same-origin protections do not address a side channel in the underlying graphics stack.
- GPU vendors and browser vendors face a coordination problem: changes that reduce observable compression behavior may affect rendering behavior or performance, while browser-only limits may constrain web compatibility.
Third-order effects
- If hardware-accelerated rendering continues to expose observable side channels, web security boundaries will increasingly depend on joint hardware, driver, and browser design rather than browser policy alone.
- The pattern broadens the security cost of heterogeneous client compute: each specialized acceleration path can become another boundary that researchers and platform owners must validate.
The trend: GPU.zip is one data point in the expansion of side-channel risk from CPUs into the heterogeneous hardware pipelines that modern browsers rely on.