Zero-click attacks in 2026: what changed and how to defend

By Greg Markowski / Jul 17, 2023 / Cybersecurity & Compliance

Zero-click attacks used to be the stuff of NSO Group exclusives, targeted at journalists and dissidents through Pegasus. That window closed. The technique has moved downmarket. Through 2024 and 2025, zero-click exploits showed up in messaging platforms, AI assistants, mobile apps, and increasingly, in software your staff use every day.

The thing that makes zero-click dangerous is the absence of human error. There is no link to click, no attachment to open, no warning sign for a trained user to spot. The exploit fires the moment a message arrives, a notification renders, or an AI agent processes content on the user’s behalf. Security awareness training does not help. Phishing simulations do not catch it. The user is compromised before they are even aware a message arrived.

If your last serious think about zero-click was in 2023 when this post was first written, the threat picture has shifted considerably. Here is what changed and what defences need to look like now.

What zero-click actually means in 2026

A zero-click exploit succeeds without any action from the target. The vulnerability is in how the receiving application parses content. Send a malformed image, a crafted protocol buffer, or a poisoned message, and the parser itself executes attacker-controlled code before the user even sees the content.

The category has expanded since the original Pegasus disclosures. Three new vectors have emerged at scale.

The first is messaging platform parsers. iMessage, WhatsApp, Signal, and Telegram all process rich content automatically. Every image preview, audio waveform render, link unfurl, and emoji reaction is parser work that runs before the user reads the message. The iMessage BLASTPASS chain disclosed in late 2023 used image processing in the ImageIO framework to bypass BlastDoor sandboxing on iOS. Apple patched it. Subsequent variants appeared through 2024 and 2025.

The second is AI assistant prompt injection. When a user asks Copilot, ChatGPT, or Claude to summarise an email or document, the AI processes the entire content including any embedded instructions. Attackers have learned to embed instructions in documents and emails that hijack the AI assistant’s behaviour, exfiltrate context, or trigger actions on the user’s behalf. The user never sees the injection, never approves the action, and never realises the AI just did something it should not have done. This is zero-click in its newest form, and the defences are still maturing.

The third is automated processing of shared content. Cloud storage scanning, email anti-malware preview, mobile device management auto-installing configuration profiles, automated ticketing system attachment indexing. Anywhere a backend system parses user-supplied content without the user being present is potential zero-click attack surface.

What changed since iMessage and BlastDoor

The 2023 zero-click conversation centred on mobile messaging and was framed as an espionage problem affecting a small number of high-value targets. The 2026 conversation is broader on three dimensions.

The target profile has widened. Through 2024 and 2025, multiple commercial spyware vendors lowered the price point of zero-click capability. The same techniques used against journalists in 2021 are now sold to private intelligence firms, divorce investigators, and competitive intelligence buyers. Australian businesses are within the affordability range of those buyers, particularly in regulated industries, professional services, and any sector with sensitive M&A or litigation exposure.

The attack surface has multiplied. Zero-click no longer requires a phone number to target a device. AI assistants processing shared documents create new attack paths that bypass traditional email and endpoint defences entirely. Document sharing within Microsoft 365, Google Workspace, and most cloud collaboration platforms creates indirect zero-click vectors that the original 2023 advice did not anticipate.

The defender maturity has lagged. Most Australian SMBs are still operating defences calibrated for the 2020-era threat model. They patch endpoints diligently and run anti-phishing on email gateways. Both are necessary. Neither addresses the AI prompt injection or the automated backend parser vectors that are doing the damage in 2026.

Where the modern attack surface actually sits

For an Australian SMB in 2026, the realistic zero-click exposure breaks down into five categories.

Mobile devices remain the highest-impact target. iOS and Android both push update cadences faster than businesses can manage. The gap between an exploit being disclosed and your fleet being patched is where the risk lives. Mobile Device Management discipline is the gating control. We will be covering Intune versus traditional MDM in a forthcoming piece, but the headline is that 30 per cent of Australian SMB mobile fleets have devices more than 60 days behind on critical patches.

AI assistants integrated into workflow tools are the fastest-growing attack surface. Every Copilot, ChatGPT Enterprise, or Claude integration that can read documents and emails is a potential prompt injection target. The exploit is not in the AI itself, it is in the contextual data the AI is allowed to see and the actions it is allowed to take. Tight permission scoping is the defence.

Email and document processing pipelines are quiet but exploitable. Any backend system that parses uploaded files (PDF, Office, image, archive) on the user’s behalf is in scope. Anti-malware engines that detonate attachments in sandboxes. Document conversion services. Optical character recognition pipelines. Each is a parser, and each parser has a history of vulnerabilities.

Messaging platforms remain a primary vector for high-value targets. iMessage, WhatsApp, Signal, Telegram, Teams, and Slack all carry the same parser-based zero-click risk. Business users moving sensitive conversations into platforms with weaker security models is its own discussion, but the technical exposure is real.

Browser-rendered content is increasingly relevant. Modern browsers parse a vast amount of structured content automatically. Web push notifications, service workers, WebRTC sessions, and embedded media all execute code in the rendering process. The exploits here are less common but the impact is higher because browsers carry session cookies for everything else.

Practical defences that actually help

The defences against zero-click in 2026 are different from the 2023 playbook. The classic advice of “patch quickly, train users, run anti-phishing” is necessary but no longer sufficient. Five practical actions matter more now.

  1. Tighten AI assistant permissions. Every AI integration in your environment should follow least privilege. Copilot should not have blanket access to every document the user can read. ChatGPT Enterprise connectors should be scoped narrowly. AI agents acting on behalf of users should never have permission to send external email or modify finance system records without explicit human approval. This is the single biggest 2026 control change.
  2. Aggressive mobile patching with enforced minimum versions. Define a maximum patch latency, usually 7 to 14 days for critical updates, and enforce it through MDM. Devices that fall behind get blocked from corporate resources until updated. This is uncomfortable for users and unforgiving on edge cases. It is also the only thing that closes the mobile zero-click window meaningfully.
  3. Restrict backend content processing exposure. Document sharing pipelines should run in segmented environments. Anti-malware sandboxes should be isolated from production identity systems. The blast radius from any single parser exploit should be limited by design.
  4. Lockdown Mode for high-value users. Apple’s Lockdown Mode dramatically reduces the iOS attack surface for users at elevated risk. Executive assistants, finance team members handling wire transfers, board members, anyone with access to material business decisions. The user experience is genuinely worse. The protection is genuinely better.
  5. Detection rather than prevention as the realistic posture. Zero-click cannot be fully prevented by current technology. Detection of post-exploitation behaviour is more achievable than blocking initial access. Modern XDR and MDR coverage is where this lives, particularly the part that watches identity behaviour, cloud access patterns, and lateral movement.

What this means for cyber insurance and compliance

Cyber insurance underwriters have started asking explicit questions about AI permission scoping and mobile patch latency. Two years ago, those were not on the questionnaire. Today, they directly affect premium and excess.

The Essential Eight does not explicitly address zero-click in its current form. The maturity model assumes a threat picture from earlier years. That said, the underlying controls (patch management, application hardening, restrict admin privileges) are the right structural defences. Our Essential 8 Compliance Guide covers how the existing controls apply to modern threats including zero-click.

The federal Privacy Act amendments coming into effect in December 2026 will tighten breach notification requirements where automated decision-making is involved. AI agents acting on user behalf without proper permission scoping create a meaningful Privacy Act exposure that did not exist in the 2023 framing.

The honest limit of what defence can do

We need to be direct about something most cyber vendors will not say. There is no defence that prevents all zero-click attacks. A determined, well-resourced attacker targeting a specific individual will find a way, and the technology gap between attackers and defenders on this category is not closing.

What you can do is reduce the attack surface, slow the attacker down, detect compromise faster, and limit the blast radius once they are in. That combination, applied diligently, moves the cost-benefit calculation against the attacker for most targets that are not specifically high-value.

For Australian SMBs, the realistic question is not “can we be perfectly secure against zero-click”. It is “can we be enough harder to compromise than the next business in our sector”. On that measure, the gap between businesses doing the five actions above and businesses still operating on 2023-era assumptions is enormous.

Frequently asked questions

What is a zero-click attack in 2026?
A zero-click attack succeeds without any action from the target. The exploit fires when a malicious message arrives, an AI assistant processes content, or a backend system parses uploaded files. There is no link to click, no attachment to open, no warning for users to spot. The most active vectors in 2026 are messaging platform parsers, AI assistant prompt injection, and automated backend content processing.
Is my business at risk of zero-click attacks?
Any business handling sensitive client data, intellectual property, financial decisions, or executives with public profiles is in scope. The targeting cost has dropped significantly since 2023, and Australian mid-market businesses are now within the affordability range of commercial spyware buyers, particularly in legal, finance, healthcare, professional services, and sectors with active M&A or litigation exposure.
How do I protect against AI prompt injection?
The primary defence is tight permission scoping on AI integrations. Copilot, ChatGPT Enterprise, and other AI assistants should follow least privilege. They should not have blanket access to all documents a user can read. They should not have permission to send external email or modify financial records without explicit human approval. The exploit is not in the AI itself, it is in the contextual data and actions the AI is allowed to access.
Does Microsoft Defender protect against zero-click?
Microsoft Defender provides partial coverage. Defender for Endpoint catches some post-exploitation behaviour. Defender for Office 365 processes email attachments in a sandbox. Neither prevents the initial parser exploit at the application layer. For zero-click protection, the broader Defender XDR suite combined with aggressive patching and AI permission scoping provides better coverage than endpoint Defender alone.
Should I enable Lockdown Mode on iOS?
Lockdown Mode dramatically reduces the iOS attack surface for high-risk users. Enable it for executives, finance team members with wire transfer authority, anyone holding material business decisions, and individuals with public profiles. The user experience is meaningfully worse, with restrictions on web browsing, message attachments, FaceTime calls from unknown contacts, and configuration profiles. The protection is real and the trade-off is justified for the high-risk profile.
How often should mobile devices be patched in 2026?
Critical security patches on mobile should be applied within 7 to 14 days of release. Enforce this through MDM by blocking corporate resource access for devices that fall behind. This is uncomfortable for users with edge-case devices and unforgiving on holiday-period gaps. It is also the only realistic way to close the mobile zero-click window. Patch latency above 30 days on critical updates is a meaningful risk for any business handling sensitive data.

Want us to assess your zero-click exposure?

We run focused assessments on AI permission scoping, mobile patch posture, and backend content processing exposure for Australian businesses. Two-week engagement, written report with prioritised remediation, no sales pressure.

Book a free zero-click exposure review

About the Author
Written by Greg Markowski, Founding Director of Epic IT, a CRN Fast50-recognised Microsoft Solutions Partner managing IT and cybersecurity for Perth businesses since 2003. Greg holds a Degree in Computer Science and a Diploma in Computer Systems Engineering from Edith Cowan University, and is ITIL certified.

Further Reading

Previous

Hybrid work security in 2026: the real attack surface

Return to News
Back to News
Next

10 signs it is time to switch your MSP in 2026 (starting with AI deployment and governance)