Researcher Says Meta Paid $78,000 Bounty for Flaw Exposing Support Data

Summary
Researcher Rony K Roy says chained authorization flaws in Meta’s support infrastructure could expose user support data and enable case changes. He says Meta patched the issue in April; Meta has not confirmed his claims.
Key points
- Roy says he reported the vulnerability to Meta in January 2026, initially assessing it as limited in severity before further analysis revealed broader impact.
- The flaws involved missing authorization, broken access control and insecure direct object references, which could be chained to enumerate support case numbers.
- An attacker could potentially access support conversations, case details, submitted files and personal information shared with Meta support.
- The flaws could also allow unauthorized support requests, workflow changes and subscribers to be added to cases.
- Roy says Meta patched the vulnerability in April and found no evidence of malicious exploitation; Meta had not confirmed his claims to SecurityWeek.
Article Details
- Vulnerability Types
- Missing authorization
- Broken access control
- Insecure direct object reference (IDOR)
- Severity
- Critical
- Exploitation Status
- not_reported
- Exploit Availability
- unknown
- Patch Status
- available
People
Vendors
Products
Meta Horizon Managed SolutionsRoy initially believed he had identified an authorization issue in Meta Horizon Managed Solutions, an enterprise platform for managing Meta Quest devices and users. It turned out to be a broader issue affecting Meta’sMeta Questan authorization issue in Meta Horizon Managed Solutions, an enterprise platform for managing Meta Quest devices and users. It turned out to be a broader issue affecting Meta’s backend support infrastructure.
