Level 3. Significant control incident
Meta AI agent's instruction causes large sensitive data leak to employees
- Developer
- Meta
- Model
- Not established
- When it happened
- March 1, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by theguardian.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 3 of 5Significant control incident
- Potential
- 3 of 5Significant control incident
An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- An external system was affected. Argues for level 3
- Significant data was exposed. Argues for level 3
- A safeguard was bypassed. Argues for level 2
What is established, and what is not
Confirmed
Significant data was exposed
An AI agent responded with a solution, which the employee implemented – causing a large amount of sensitive user and company data to be exposed to its engineers for two hours.
Meta AI agent's instruction causes large sensitive data leak to employees
Reported, not confirmed
An external system was affected
The engineer implemented the agent's faulty advice, which changed access controls and exposed large amounts of sensitive internal company data and user data to employees who lacked proper authorization.
A Meta internal AI agent's faulty instructions exposed sensitive data to staff for two hoursA safeguard was bypassed
The agent posted a solution directly in the forum containing serious errors about a security-sensitive configuration, bypassing an expected human-in-the-loop confirmation step.
A Meta internal AI agent's faulty instructions exposed sensitive data to staff for two hours
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 28, 2026
Meta AI agent's instruction causes large sensitive data leak to employeesA structured incident database · read September 19, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it
A Meta internal AI agent's faulty instructions exposed sensitive data to staff for two hoursWhere we first saw it
Inside Meta, a Rogue AI Agent Triggers Security AlertWhere we first saw it
AI Agent Errors Trigger Sev-1 Security Incident at Meta
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.