Loading story…
Meta remediated a critical authorization flaw in its customer support infrastructure after independent researcher Rony K. Roy found that backend GraphQL operations did not consistently verify support case ownership. The weakness, first identified while testing Meta Horizon Managed Solutions, reportedly extended into broader Meta.com support workflows and created an IDOR-style exposure because support case IDs were sequential and predictable. Sensitive records that could have been accessed included emails, live chats, attachments, internal case metadata, and other personally identifiable information.
Roy said the vulnerability chain also enabled unauthorized actions beyond data access, including creating support requests for other organizations, changing case status, and adding external subscribers to cases. Meta was notified in January 2026 and completed remediation in April, and the company said it found no evidence of malicious exploitation in the wild. Roy reported receiving a $78,000 bug bounty for the discovery, while reporting indicated the issue stemmed from Meta’s authorization logic rather than any underlying Salesforce-backed support components.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Rony K. Roy said he received a $78,000 bug bounty for the Meta support infrastructure vulnerability. One source reports the award directly, while another notes Meta did not publicly confirm the payout.
Meta completed remediation of the reported support infrastructure flaws in April 2026. The company said it found no evidence that the vulnerability had been exploited in the wild.
Independent researcher Rony K. Roy reported a chain of authorization weaknesses in Meta's customer support infrastructure in January 2026. The issues could have exposed support records and enabled unauthorized actions such as creating or modifying support cases for other organizations.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Meta disclosed an internal **Sev 1 security incident** after an engineer followed troubleshooting advice generated by an AI agent on an internal forum, causing large volumes of company data to become accessible to unauthorized employees for more than two hours. Reporting cited by *IT Pro* and *The Guardian* said the exposure affected sensitive internal data and spread access beyond the intended group of engineers, raising concerns about how AI-generated operational guidance can directly alter permissions and data handling inside enterprise environments. Meta said an incident occurred but maintained that **no user data was mishandled**. The case has been highlighted as a warning about **agentic AI** in corporate settings, where staff may act on plausible but unsafe recommendations without adequate review. The reporting also underscored broader security issues tied to AI agents, including excessive access, weak validation of automated guidance, and identity governance challenges involving non-human accounts and systems.
Jun 29, 2026
Searchlight Cyber disclosed multiple patched vulnerabilities in **Salesforce Marketing Cloud (SFMC)** that could have exposed private email data across hundreds of organizations on Salesforce’s shared infrastructure. The issues affected **AMPScript**, **SSJS**, **CloudPages**, email rendering, and legacy tracking and email-view links, creating paths for template injection, subscriber enumeration, access to internal data views, and forged or decrypted tracking parameters. Researchers said one key flaw came from double evaluation of AMPScript in email subject lines, allowing unsanitized subscriber input to be executed during rendering, while another involved argument injection through the `MicrositeURL` function. Researchers also found weak protections on legacy links, including a static XOR-based scheme and unauthenticated CBC encryption that could act as a padding oracle, enabling decryption and forgery of links and raising the risk of **cross-tenant** access to sent email content, contact lists, SMS records, and click-tracking data. Salesforce said the flaws were reported on **16 January 2026** and mitigated between **21 and 24 January**, including disabling subject-line double evaluation, migrating Marketing Cloud Engagement encryption to **AES-GCM**, rotating keys, and invalidating older tracking, CloudPages, and email-view links created before **21 January 2026 23:00 UTC**; the company said it found no confirmed unauthorized customer data access or malicious exploitation.
Jun 29, 2026
Meta paused work with AI hiring startup Mercor after Mercor disclosed a breach tied to the malicious `LiteLLM` packages `1.82.7` and `1.82.8`, which were published to PyPI after attackers stole the project’s publishing token through a compromised CI/CD chain involving Trivy tooling. Security reporting said the tainted packages harvested credentials and deployed a multi-stage backdoor capable of stealing API keys, cloud credentials, SSH keys, Kubernetes tokens, CI/CD secrets, database passwords, and other sensitive data, leading responders to treat affected environments as fully compromised. Mercor said the incident exposed source code and candidate information, while reports citing the attackers said as much as **4TB** of data was taken, including candidate profiles, personally identifiable information, employer data, and API keys, with one claim alleging access via `Tailscale` VPN. The fallout spread quickly across Mercor’s customers and partners: Meta reportedly froze contracts indefinitely while investigating whether AI training data or related secrets were at risk, OpenAI reviewed its own exposure while keeping contracts in place, and the breach triggered lawsuits and broader scrutiny of software supply-chain risk across the AI ecosystem.
Jun 29, 2026