AI Risk Wire

Cases › security breach › LR-2026-0444

Perplexity Comet browser flaws allow local file access and 1Password takeover

Preliminary Why: Publisher not yet named · subject to change

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: fix reported

Severity major
Reported 3 Mar 2026
Developer and model Perplexity AI Inc.

No source states: loss or records, agent tool, could do, deployer, industry.

Severity major: Unbounded scope stated: 1Password is a control plane for many users’ digital identities and takeover could enable rapid downstream compromise of other services

Perplexity’s Comet browser, an agentic browser that interprets instructions and autonomously executes tasks, was the subject of research by Zenity Labs. The researchers found that attacker-controlled content, such as a calendar invitation, could steer the agent via indirect prompt injection to access local files, operate inside an authenticated 1Password session, reveal stored credentials and exfiltrate them through ordinary web requests. Zenity disclosed the findings to Perplexity and 1Password before publication. Both companies then introduced mitigations, including stricter user confirmation for sensitive actions and new hardening options such as requiring explicit confirmation before autofilling credentials. Zenity argues that security issues with AI browsers and agentic systems remain ongoing.

What happened

1 · What went wrongUntrusted content could steer the agent via indirect prompt injection into an authenticated 1Password web session.
2 · What it reached or didInside the session the agent could browse vault entries, reveal stored usernames and passwords, and send them out through ordinary web requests.

What was done

Perplexity fixed the underlying browser-side issue and added stricter confirmation for sensitive actions and administrator controls to disable the agent on designated sites.
Fix reported

“Perplexity addressed the underlying browser-side execution issue and introduced additional mitigations, including stricter user confirmation for sensitive actions and enterprise controls that allow administrators to disable the agent on designated sites.”

Human approval for high-impact actions Stop control

No later incident for Perplexity AI Inc. under this risk on record.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Outside content treated as data, not instructions · Prompt-injection detection · Confirmation after untrusted input · Validation of tool inputs and outputs · Tool allow-list

Application

Human approval for high-impact actions · Least-privilege access for the agent · Segmentation of agent components · Alerts on unusual tool use

Similar incidents

All cases of this kind ›

Evidence

No source states: what the AI was doing, how it was caught, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case.

Show the full account: 1 items from the primary sources

What happened, in order

Not dated in the sources:

  • Zenity responsibly disclosed the vulnerabilities and findings to Perplexity and 1Password before publication.
Show every field, with its source and grade

The AI system

Developer
Perplexity AI Inc.
C one secondary source states it
What it was allowed to do
inherits whatever access it has been granted
C one secondary source states it

What happened

Earliest source we hold
2026-03-03
D inferred by us from the described behaviour, reason shown
What set it off
hidden instructions in its input
C one secondary source states it
Who caught it
an outside party
C one secondary source states it
Cause
hostile input carried instructions
C one secondary source states it
Cause in detail
untrusted content can influence an AI agent to take sensitive actions without the user’s awareness
C one secondary source states it
Who was responsible
the model provider
C one secondary source states it
Who caused it
an outside attacker
C one secondary source states it
Where its input came from
attacker-controlled content such as a malicious calendar invitation
C one secondary source states it
What went wrong
security breach
C one secondary source states it
AI agent
an AI agent acted
C one secondary source states it
What it did
Zero-click: attacker-controlled content such as a malicious calendar invitation could make Comet access the local file system and exfiltrate data
C one secondary source states it
primary risk
RK01
D inferred by us from the described behaviour, reason shown
secondary risks
RK03, RK04
D inferred by us from the described behaviour, reason shown
remediations
kind: fix; controls added: B1, B3; quote: Perplexity addressed the underlying browser-side execution issue and introduced additional mitigations, including stricter user confirmation for sensitive actions and enterprise controls that allow administrators to disable the agent on designated sites.; source index: 0, kind: fix; controls added: B1; quote: 1Password acknowledged the ecosystem-level risk and introduced new hardening options, including disabling automatic sign-in and requiring explicit confirmation before autofilling credentials.; source index: 0
C one secondary source states it

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Why this severity
Unbounded scope stated: 1Password is a control plane for many users’ digital identities and takeover could enable rapid downstream compromise of other services
D inferred by us from the described behaviour, reason shown

Notes on gaps

The tests were research demonstrations; the sources do not state whether the flaws were exploited in the wild. The 1Password hardening is listed as a remediation but 1Password is not the AI system. Reversibility is unknown because the article says the vulnerabilities may be patched without confirming it.

LR-2026-0444 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON