Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SSRF vulnerability on proxy.duckduckgo.com (access to metadata server on AWS)Analysed#395521 | Valid | No weakness recorded | Critical | 2018-10-31 | – | 25 |
| DOM XSS on duckduckgo.com searchAnalysed#921635 | Valid | Cross-site Scripting | Medium | 2020-08-20 | – | 30 |
| RCE + Supply Chain Attack via pull_request_target in content-scope-scripts/semver-label.yml — Affects All DuckDuckGo BrowsersAnalysed#3619287 | Valid | No weakness recorded | Critical | 2026-06-11 | – | 41 |
| RCE + PAT Exfiltration via pull_request_target in privacy-configuration/auto-respond-pr.yml — Direct Supply Chain to All DDG BrowsersAnalysed#3619288 | Valid | No weakness recorded | Critical | 2026-06-11 | – | 66 |
| DOM XSS on duckduckgo.com searchAnalysed#876148 | Valid | Cross-site Scripting | Medium | 2020-06-26 | – | 74 |
| Reflected/Stored XSS on duckduckgo.comAnalysed#1110229 | Valid | Cross-site Scripting | High | 2021-04-10 | – | 135 |
| Partial bypass of #483774 with Blind XXE on https://duckduckgo.comAnalysed#486732 | Valid | Injection and Smuggling | High | 2019-02-25 | – | 159 |
| SSRF on duckduckgo.com/iu/Analysed#398641 | Valid | Server-Side Request Forgery | High | 2018-09-09 | – | 165 |
| XXE on https://duckduckgo.comAnalysed#483774 | Valid | Injection and Smuggling | Critical | 2019-01-31 | – | 218 |
| DOM XSS on duckduckgo.com searchAnalysed#868934 | Valid | No weakness recorded | High | 2020-06-14 | – | 326 |
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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.