The curl quirk that exposed Burp Suite & Google Chrome

Summary: PortSwigger Research disclosed that a documented curl feature, where a request body or header starting with an @ symbol is read as a local file, led to a local-file disclosure vulnerability in both Burp Suite Pro and Google Chrome. The issue was privately reported through PortSwigger's bug bounty program by Paul Mutton, and Burp Suite was patched in release 2020.5.1 by switching to the --data-raw flag when a request body starts with @.
What's compelling: Exploiting it in Burp Suite required heavy user interaction - visiting a malicious site, copying a crafted request as a curl command, and running it - but a website that passes an attacker-controlled request body to curl could face significantly higher impact, which the researchers flag as worth watching during SSRF testing.

Read the original at PortSwigger Research ↗

Topics: Vulnerabilities & Patching
Related: Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026
U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026