Executive Summary
In September 2026, security researcher Gal Weizman discovered BragJack, a novel attack method that compromises agentic AI assistants built into popular browsers including Google Chrome with Gemini, Microsoft Edge with Copilot, Opera Neon, Perplexity Comet, and Claude in Chrome. The attack exploits architectural flaws in how these browsers handle communication between extensions and AI agents, allowing malicious extensions to hijack the AI's functionality without relying on traditional prompt injection techniques. Attackers can force the compromised AI agents to access sensitive information, execute unauthorized actions, take screenshots, access local files, activate cameras and microphones, and exfiltrate data from any authenticated websites. The vulnerabilities affected hundreds of millions of users and earned over $20,000 in bug bounties, with Google and Microsoft issuing CVEs CVE-2026-0628 and CVE-2026-55945 respectively.
This incident highlights the emerging security risks as AI agents become more integrated into everyday browser experiences and demonstrates the critical need for secure architectural design in agentic systems before widespread deployment.
Why This Matters Now
BragJack represents a new class of AI agent attacks that bypass traditional security measures as organizations rapidly adopt agentic AI systems. With browsers increasingly integrating AI assistants and enterprises deploying autonomous agents, understanding and defending against architectural flaws that enable AI hijacking is critical for preventing data exfiltration and unauthorized system access.
Attack Path Analysis
The BragJack attack exploits architectural flaws in agentic browsers to hijack communication channels between extensions and AI agents. Attackers compromise browser extensions to bypass trust boundaries, escalate privileges through AI agent manipulation, establish command channels via compromised agent communications, and exfiltrate sensitive data including emails and files through the hijacked AI assistant.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attacker exploits browser extension vulnerabilities to bypass trust boundaries between untrusted extensions and privileged AI agents, targeting Chrome/Gemini, Edge/Copilot, Opera Neon, Perplexity Comet, and Claude browsers
Related CVEs
CVE-2026-0628
CVSS 8.8A privilege escalation vulnerability in Google Chrome's agentic AI implementation allows browser extensions to bypass security boundaries and control the Gemini AI agent to access sensitive data and execute malicious actions.
Affected Products:
Google Chrome Browser with Gemini AI – < patched version
Exploit Status:
proof of conceptCVE-2026-55945
CVSS 4.2A security boundary bypass vulnerability in Microsoft Edge's Copilot implementation allows malicious extensions to hijack AI agent communication channels through race conditions between Think and Do modes.
Affected Products:
Microsoft Edge Browser with Copilot – < patched version
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Drive-by Compromise
Process Injection
Browser Session Hijacking
Input Capture: Keylogging
Application Layer Protocol: Web Protocols
Exfiltration Over C2 Channel
Create or Modify System Process: Windows Service
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Software Security Testing
Control ID: 6.4.2
NYDFS 23 NYCRR 500 – Penetration Testing
Control ID: 500.15
DORA – Testing of ICT Risk Management
Control ID: Article 8
CISA ZTMM 2.0 – Organizational Communication and Data Flows
Control ID: ID.AM-3
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21.2.a
ISO 27001:2022 – Secure Development Policy
Control ID: A.14.2.1
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Browser hijacking attacks targeting agentic AI systems expose software development environments to code theft, intellectual property exfiltration, and compromised development workflows through malicious extensions.
Financial Services
BragJack attacks can access authenticated banking sessions, steal financial correspondence, and perform unauthorized transactions by hijacking browser-based AI agents in financial institutions.
Health Care / Life Sciences
Healthcare organizations face HIPAA compliance violations as hijacked browser agents can access patient records, medical correspondence, and sensitive healthcare data through compromised agentic browsers.
Information Technology/IT
IT organizations managing enterprise browser deployments face widespread exposure as hundreds of millions of users with browser extensions become vulnerable to AI agent hijacking attacks.
Sources
- BragJack Attack Can Turn a Browser's Agentic AI Against Ithttps://www.darkreading.com/endpoint-security/bragjack-browser-agentic-aiVerified
- Forever Security BragJack Research Bloghttps://foreversecurity.com/bragjack-researchVerified
- Google Chrome Security Advisory - CVE-2026-0628https://chromereleases.googleblog.com/security-advisory-cve-2026-0628Verified
- Microsoft Security Response Center - CVE-2026-55945https://msrc.microsoft.com/security-advisory-cve-2026-55945Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely constrain the BragJack attack's ability to exploit browser-based AI agent communications through network segmentation and controlled access paths. The attack's reach across authenticated sessions and external communications would be significantly reduced through east-west traffic controls and egress policy enforcement.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Network segmentation would likely limit the compromised browser extension's ability to communicate with backend AI services and reduce the attack surface available for exploitation.
Control: Zero Trust Segmentation
Mitigation: Microsegmentation policies would likely constrain the attacker's ability to escalate privileges across different application contexts and limit access to AI agent privileged functions through workload isolation.
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely restrict the compromised AI agent's ability to access multiple authenticated sessions and constrain lateral movement between different web services and applications.
Control: Multicloud Visibility & Control
Mitigation: Network visibility and control mechanisms would likely detect and constrain abnormal communication patterns between compromised AI agents and external command infrastructure, reducing persistent access capabilities.
Control: Egress Security & Policy Enforcement
Mitigation: Egress filtering and data loss prevention policies would likely constrain the volume and scope of sensitive data exfiltration by restricting outbound communications from compromised AI agents.
Despite network controls, the attacker may still perform limited destructive operations within already compromised browser sessions, though the scope would likely be constrained to individual user contexts rather than enterprise-wide impact.
Impact at a Glance
Affected Business Functions
- Web browsing security
- AI-assisted productivity tools
- Browser extension management
- Data privacy controls
Estimated downtime: 1 days
Estimated loss: N/A
Sensitive information accessible through browser agents including email correspondence, authentication tokens, local files, camera and microphone access, and data from websites where users are authenticated. Potential for data exfiltration to attacker-controlled endpoints.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Cloud Native Security Fabric (CNSF) controls to provide real-time inspection and autonomous enforcement against agentic AI abuse and shadow AI risks
- • Deploy egress security and policy enforcement to prevent unauthorized data exfiltration from compromised browser agents to external destinations
- • Establish zero trust segmentation with identity-based policies to limit AI agent access to sensitive resources and implement least privilege principles
- • Enable multicloud visibility and control with centralized policy management to detect anomalous interactions and suspicious automation patterns from browser agents
- • Implement threat detection and anomaly response capabilities with baselining to identify compromised browser agent behavior and trigger incident response procedures



