Skip to content

Bug bounty reports15,219

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

Program:curl
Status
Severity
Weakness:Server-Side Request Forgery
Clear
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Abusing URL Parsers by long schema name#1049624InformativeServer-Side Request ForgeryNone2021-01-08–3
SSRF via maliciously crafted URL due to host confusion#704621InformativeServer-Side Request ForgeryCritical2021-01-08–6
CVE-2022-27780: percent-encoded path separator in URL host#1553841ValidServer-Side Request ForgeryMedium2022-05-11–9
Gopher Protocol Command Injection (SSRF Smuggling)#3508785N/AServer-Side Request ForgeryHigh2026-01-14–9
IDN decoding inserts authority delimiters and can redirect proxy CONNECT to a different host#4129950InformativeServer-Side Request ForgeryHigh2026-10-21–12
curl-ipv4-percent-normalization-SSRF#3791168InformativeServer-Side Request ForgeryMedium2026-06-10–13
50: CMake `HTTP_ONLY` does not disable SSH backends — SCP and SFTP remain usable#3973228InformativeServer-Side Request Forgery–2026-08-29–13
Unsanitized IPFS CID Allows SSRF Against Configured Gateway#3366484N/AServer-Side Request ForgeryMedium2025-10-03–34

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.