Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Snapchat
Status
Severity
Weakness:Access Control
Clear
Year
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Publicly accessible Continuous Integration ToolAnalysed#313457ValidAccess ControlCritical2021-07-29–562
RCE/LFI on test Jenkins instance due to improper authentication flowAnalysed#258117ValidAccess ControlMedium2017-08-19–118
Client IP Spoofing using "X-Forwarded-For: 127.0.0.1" on "studio-app.snapchat.com" exposing bucket detailsAnalysed#382678ValidAccess ControlHigh2021-08-12$50040
Domain Takeover in [obviousengine.com] a snapchat acquisitionsAnalysed#392785ValidAccess ControlHigh2018-10-07–32
Organization Members in Snap Kit may Deactivate AppsAnalysed#1103448ValidAccess ControlLow2021-08-26–26
Subdomain Takeover via unclaimed UserVoice domainAnalysed#269109ValidAccess ControlHigh2017-10-04$25018
Password Reset - query param overrides postdata#96636ValidAccess Control–2015-12-24$1,50012

Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report, where there is one, which can be wrong. Data as of 2026-11-15.