Root cause
The vendor says a support-system misconfiguration let support workflows reach internal documentation. The public summary does not disclose the configuration, required authentication or how permissions were passed between systems. Describing this as a failure to keep identities within their allowed access is a defensive interpretation, not a documented implementation detail.
Demonstrated impact
The vendor confirms access to nonpublic internal documentation and the ability to view and modify limited Confluence content. It does not establish unrestricted administrative control, the volume of material exposed, or broader compromise. The timeline records accepted retesting and Resolved status on June 3, 2025; redacted comment bodies do not reveal the corrective configuration or exact deployment date.
What to check for
- Assess whether external support workflows can confer access to employee-only documentation.
- Review integration permissions separately for read and write access; limited modification is distinct from unrestricted control.
- Verify the corrected access boundary after configuration changes without treating a resolution status as evidence of the precise fix.
Award and evidence
How the award was verified, and what the record does not establish
Dollar notation appears in the report UI; USD denomination is contextual from HackerOne’s disclosure policy. Award events do not establish cash receipt. One-report total: USD 5,000 to red_darkin and USD 7,500 to madara_; neither recipient individually received USD 10,000.
- Award events establish an award, not independently audited settlement.
- Exact fix-deployment date is unavailable; a Resolved status date is not treated as deployment.
- Technical report and comment bodies are redacted; interpretation is limited to the vendor’s public summary and event metadata.
- Exact access prerequisites and the corrective configuration are not disclosed; no specific identity provisioning or entitlement mechanism is established by the public summary.
Timeline
- Published
- 2025-08inferred · Disclosure events appear August 13 and August 15, 2025. The sidebar shows August 15; month retained because first public day is ambiguous.
- Public Disclosure
- 2025-08inferred · Disclosure events appear August 13 and August 15, 2025. The sidebar shows August 15; month retained because first public day is ambiguous.
- Reported
- 2025-04-26explicit
- Awarded
- 2025-05-30explicit
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
- Framework serialization change exposed private HackerOne user attributes
HackerOne · Information exposure and response privacy · USD 25,000
Sources
- Support integration exposed internal Confluence documentation (report 3113398)HackerOne and the credited researchers · reviewed 2026-10-03
- Vulnerability Disclosure Standards: Bug Bounty payment denominationHackerOne · reviewed 2026-10-02
Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.