Attackers broke into Android phones by combining a memory flaw in the Chrome browser engine with a separate vulnerability in Qualcomm's Snapdragon GPU driver. The most striking part of the attack is that the victim never had to tap on anything: simply opening a crafted web page was enough. In security literature, this is called a "zero-click" attack.

What happened?

The incident stems not from a single flaw but from a chain. The first link is a memory bug in Chrome's rendering engine; this flaw lets malicious code run inside the browser's restricted area. The second link is the vulnerability in the Snapdragon GPU driver. The attacker takes the initial foothold gained inside the browser and escalates it to kernel privileges through the GPU driver. The end result is top-level control over the phone.

Why does it matter?

The real issue here isn't a single CVE but the architecture of the chain. Modern mobile operating systems are built on layered defenses: the browser runs in its own sandbox, apps are isolated from one another, and the kernel is protected separately. A single flaw usually isn't enough to break through these layers. What the attacker did was find a separate key for each layer and use them in sequence. The browser flaw cracks the door open, while the GPU driver flaw punches through the isolation wall.

It's no coincidence that GPU drivers keep playing a role in these chains. For the sake of performance, graphics drivers run very close to the hardware, at a low level, with broad privileges. Their codebases are large and complex; memory management is mostly done by hand in C/C++. That makes the GPU driver an attractive and recurring attack surface on widespread chips like Snapdragon. Given Qualcomm's dominance in the Android market, a single driver flaw can affect hundreds of millions of devices at once.

The second major dimension is economic. Zero-click chains of this quality are hard to find and expensive. Exploits like these typically circulate in the economy of commercial spyware firms and state-backed actors, used in operations targeting journalists, activists, or high-profile targets. In other words, this isn't a phishing lure thrown at random users; it's a targeted, capital-intensive type of attack. The same model we saw in Pegasus-style cases applies here as well.

Who does it affect, and how?

For the average user, the immediate risk appears low; because these chains are expensive, they aren't scattered across a broad audience. But for high-risk individuals, the picture is different.

LayerVulnerabilityPrivilege gained
Chrome engineMemory flawCode execution inside the browser
Snapdragon GPU driverDriver vulnerabilityEscalation to kernel privileges
Operating systemResult of the chainFull control over the device

For comparison: older-generation attacks relied on the user clicking a link or opening a file. Zero-click chains eliminate this human link entirely. Being careful no longer provides protection on its own; the burden of defense shifts largely to patching speed.

What's next?

The most critical defense is staying up to date. Keeping Chrome set to update automatically and installing system and security patches as soon as they arrive closes the links of this chain one by one. Older Android devices that have stopped receiving updates are the most fragile group at this point; phones whose manufacturer support has ended may never receive GPU driver patches at all.

The real trend to watch is the security of the GPU and hardware-adjacent driver layer. Google and Qualcomm moving to memory-safe languages at this layer and streamlining driver code could narrow this attack surface over the long term. In the short term, the most realistic assessment is this: as long as zero-click chains remain technically possible, the only effective lever in the user's hands is patch discipline — and that is a responsibility tied far more to the manufacturer's update speed than to the user.