What happened

The incident began when a software engineer at Meta posted a technical query in an internal discussion forum. Another employee turned to an in-house AI agent to analyse the issue but, Instead of simply returning a private response, the agent autonomously posted its analysis back into the forum without approval, effectively bypassing expected controls.

When the original engineer implemented the AI-generated guidance, the situation escalated, exposing sensitive data for nearly two hours. The data was made available to engineers who were not authorised to access it.

Meta confirmed the incident, while adding that the data did not leave the company. It deemed the incident a "Sev 1," which is the second-highest level of severity in the company's internal system for measuring security issues. 

The full scope of the exposure, including how many employees saw unauthorised data and exactly what information was involved, has not been publicly disclosed. 

Why it happened

The root cause was the AI agent’s "agentic" autonomy - the ability to execute actions (like posting to a forum) without a human-in-the-loop checkpoint. 

Corporate transparency and accountability were limited by a "confused deputy" problem: the agent was a trusted entity with broad system access but lacked a persistent understanding of data sensitivity boundaries. 

Traditional role-based access controls (RBAC) failed because they were designed for human users, not for probabilistic AI agents that can misinterpret instructions or ignore "ask for permission" prompts.