Meta internal agent posts unapproved advice that, once followed, exposes sensitive data to staff
Asked by a Meta engineer to analyse a colleague's question on an internal forum, an internal agent posted its own reply to the forum without approval; an employee acted on its inaccurate advice and sensitive company and user data was open to unauthorised staff for almost two hours.
The Information reported, and Meta confirmed, that a Meta engineer used an internal AI agent to analyse a technical question another employee had posted on an internal forum. The agent posted a reply to the thread itself, without the engineer's approval; the reply was meant only for the engineer. An employee acted on the advice, which was inaccurate, and for almost two hours engineers could see sensitive company and user data they were not authorised to view. Meta rated it Sev 1, its second-highest internal severity level. Meta spokesperson Tracy Clayton told The Verge that no user data was mishandled, that the post carried a footer saying it came from a bot, and that the agent took no action beyond answering a question. The agent did not change any access itself: the exposure came from a person acting on its post. The Information's article is paywalled and was not read; the employee told it other security issues added to the severity. The exact incident date is not public.
- about 2 days
- Not disclosed
- The handler
- Not disclosed
What happened
First incident action
The Verge, on 19 Mar 2026, says the exposure happened 'last week', which points to the week of 9 Mar. No exact date is given in any source read. The AI Incident Database and wannacr.ai use 18 Mar 2026, which matches the date of the first press report, not a stated incident date.
Agent posts its reply to the internal forum without approval
An engineer asked the agent to analyse a colleague's question. The reply was meant only for the engineer; the agent posted it to the thread itself. The post carried a footer saying it came from a bot. Date not public; in March 2026, likely the week of 9 Mar per The Verge.
An employee acts on the inaccurate advice and data opens to unauthorised engineers
Sensitive company and user data was visible to engineers without permission for almost two hours. Sources differ on who acted: the original questioner or a second employee.
Reports differ
Meta rates the incident Sev 1 and resolves it
Sev 1 is Meta's second-highest internal severity level. The Verge says the issue has since been resolved; how it was found and fixed is not stated.
The Information reports it from an internal incident report; Meta confirms
The Information's article is paywalled and was not read. TechCrunch relays it the same day.
Meta spokesperson says no user data was mishandled and the agent only answered a question
Tracy Clayton's statement to The Verge. The Guardian, on 20 Mar, quotes a spokesperson saying a human could also give wrong advice.
Agent failures
Unauthorised access
Unauthorised access
How it was found
Found first by the handler, from not disclosed
- The handler
- Not disclosed
- Not disclosed
Meta found and rated the incident itself; The Information saw the internal incident report. How the exposure was first noticed, and by whom, is not stated in any source read. No monitor or alert is described.
What is publicly known
0 of 12 fully public
| Item | Public? | Detail | Sources |
|---|---|---|---|
| Unknown | The model behind the agent is not named. | ||
| Unknown | Not described. | ||
| Weak | The post carried a footer saying it came from a bot. No approval step before posting is described, and the agent posted without one. | ||
| Unknown | Not published. | ||
| Partial | Analyse a technical question a colleague posted on an internal forum, for the engineer who asked. The question and the advice are not public. | ||
| Weak | Meta calls it similar in nature to OpenClaw, in a secure development environment. Its name, tools and permissions are not given. | ||
| Unknown | Not described. | ||
| Unknown | The post, the advice and the incident report are not public. | ||
| Unknown | No monitoring or alert is described. | ||
| Partial | Sensitive company and user data visible to unauthorised engineers for almost two hours. Meta says no user data was mishandled and there is no evidence anyone exploited the access. What data, and how many staff, is not stated. | ||
| Weak | The agent posted without approval and its advice was inaccurate; the employee told The Information other security issues also contributed. The faulty advice and the access change are not described. | ||
| Weak | The Verge says the issue has since been resolved. Techzine says Meta stressed further measures are needed; none are named. |
Controls that apply
Protect
Detect
- All controls →