Root cause
A client-specific error path retrieved media under an elevated service identity, losing the original requester’s privacy constraints.
Demonstrated impact
Private post text and media could be exposed. The researcher did not establish the same effect for profile embedding.
What to check for
- Preserve requester authorization across error handling and fallback paths.
- Keep policy decisions consistent across client-specific code paths.
- Distinguish demonstrated data exposure from unverified adjacent features.
Award and evidence
How the award was verified, and what the record does not establish
One report: 10,000 base plus 2,000 and 2,500 bonuses. Classified as a bug bounty with event bonuses, not a separate placement prize. The article uses $; USD is contextualized by Facebook’s official program and BountyCon reporting, which predates this award.
- Researcher-reported award, not independent vendor confirmation or audited settlement.
- Currency context comes from an earlier official program retrospective, not a reproduced award receipt.
- The account-restriction root cause is the researcher’s account of vendor clarification.
Timeline
- Published
- 2023-10-12explicit
- Reported
- 2022-09-20explicit
- Awarded
- 2022-09-25explicit · All three report-linked reward components share this timeline date.
Related cases
- Google Mamba temporary outputs lacked access isolation
Google · Authorization and tenant boundaries · USD 37,604.40
- Google Firefly confused worker authority and storage boundaries
Google · Authorization and tenant boundaries · USD 60,000
- Google Application Integration mixed resource and service authority
Google · Authorization and tenant boundaries · USD 75,000
- Google support API exposed customer and agent data
Google · Authorization and tenant boundaries · USD 14,337
- Meta service-identity exposure amplified by excessive secret access
Meta · Cloud permissions and isolation · USD 150,000
- Meta Quest login migration lost OAuth credential confinement
Meta · Authentication and identity · USD 44,250
Sources
- How I Exposed Instagram's Private Posts by Blocking Users003random · reviewed 2026-10-02
- Facebook Bug Bounty and BountyCon US-dollar reportingDan Gurfinkel / Facebook · reviewed 2026-10-02
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.