Root cause
Authentication established a caller but did not bind the requested media object to that caller. The researcher’s two-user comparison exposed this distinction between feature access and content authority.
Demonstrated impact
The demonstration disclosed another user’s original prompt and generated media. Broader data harvesting was potential impact; the reproduced vendor response reports no evidence of abuse.
What to check for
- Preserve ownership checks across derived-media and editing operations.
- Distinguish temporary mitigation, full-fix confirmation and actual deployment timing.
Award and evidence
How the award was verified, and what the record does not establish
The researcher explicitly states USD and reproduces the vendor award decision. Settlement is unverified.
- Vendor wording is researcher-published, not independent vendor confirmation.
- An updated date does not establish original publication. Full-fix confirmation does not establish deployment timing.
- Cash receipt is not established.
- The article attributes remediation to ownership checks but does not supply an independently reviewed patch.
Timeline
- Reported
- 2024-12-26explicit
- Mitigated
- 2025-01-24explicit · Timeline labels this a temporary fix.
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
- Meta AI prompts and generated content: technical analysisSandeep / AppSecure · reviewed 2026-10-03
Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.