{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","feed_url":"https://feed.craftedsignal.io/tags/fastcgi/feed.json","home_page_url":"https://feed.craftedsignal.io/","items":[{"_cs_actors":[],"_cs_cpes":[],"_cs_cves":[],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["HAProxy (through 3.4.0)"],"_cs_severities":["high"],"_cs_tags":["vulnerability","haproxy","fastcgi","integer-overflow","webserver","proxy"],"_cs_type":"advisory","_cs_vendors":["HAProxy"],"content_html":"\u003cp\u003eCVE-2026-55203 impacts HAProxy versions up to and including 3.4.0, stemming from an integer overflow within the \u003ccode\u003efcgi_conn\u003c/code\u003e structure's \u003ccode\u003edrl\u003c/code\u003e field. This vulnerability is triggered when HAProxy receives a FastCGI record from a backend where \u003ccode\u003econtentLength\u003c/code\u003e is precisely 65535 and \u003ccode\u003epaddingLength\u003c/code\u003e is 1 or more. Under these specific conditions, the \u003ccode\u003edrl\u003c/code\u003e field wraps to 0, causing HAProxy to misinterpret subsequent data as new FastCGI record headers. This desynchronization of the FCGI framing parser enables malicious FastCGI backends to manipulate HAProxy's internal state, potentially resulting in request routing errors, response smuggling, or various memory safety issues. Organizations utilizing HAProxy as a reverse proxy for FastCGI applications are particularly susceptible, making immediate patching crucial.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker establishes or compromises a FastCGI backend service configured to communicate with a vulnerable HAProxy instance.\u003c/li\u003e\n\u003cli\u003eThe malicious FastCGI backend constructs and sends a specially crafted FastCGI record to HAProxy.\u003c/li\u003e\n\u003cli\u003eThe crafted FastCGI record includes a \u003ccode\u003econtentLength\u003c/code\u003e value of 65535 and a \u003ccode\u003epaddingLength\u003c/code\u003e of 1 or more.\u003c/li\u003e\n\u003cli\u003eHAProxy receives and attempts to process this record, triggering an integer overflow in the \u003ccode\u003efcgi_conn\u003c/code\u003e structure's \u003ccode\u003edrl\u003c/code\u003e field, causing the field to wrap to 0.\u003c/li\u003e\n\u003cli\u003eDue to the \u003ccode\u003edrl\u003c/code\u003e field's incorrect value, HAProxy misinterprets the subsequent data stream from the backend as new FastCGI record headers.\u003c/li\u003e\n\u003cli\u003eThis misinterpretation desynchronizes HAProxy's internal FastCGI framing parser, leading to incorrect consumption of subsequent records.\u003c/li\u003e\n\u003cli\u003eThe desynchronization allows the attacker to control HAProxy's processing, potentially leading to request routing errors (e.g., client request routed to wrong backend), response smuggling (e.g., appending arbitrary content to legitimate responses), or various memory safety issues (e.g., crashes, arbitrary code execution).\u003c/li\u003e\n\u003cli\u003eThe ultimate objective is achieved, ranging from data manipulation, unauthorized access, to denial of service or remote code execution depending on the specific memory safety issue exploited.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eThe successful exploitation of CVE-2026-55203 can lead to severe consequences, with a CVSS v3.1 Base Score of 7.5. Primary impacts include the desynchronization of HAProxy's FastCGI parser, enabling attackers to cause request routing errors, potentially redirecting user traffic to unintended services or malicious content. More critically, it can facilitate response smuggling, where attackers can inject arbitrary data or even entire unauthorized responses into a legitimate client's connection. Furthermore, the underlying integer overflow can lead to various memory safety issues, potentially resulting in HAProxy crashes, denial-of-service, information disclosure, or even remote code execution, undermining the stability and security of the proxy layer.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003ePatch CVE-2026-55203 immediately by updating HAProxy to a version beyond 3.4.0 (e.g., 3.4.1 or later containing commit 5985276).\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026quot;CVE-2026-55203 - Detect HAProxy FCGI Parsing Errors\u0026quot; to your SIEM to identify internal errors indicative of attempted exploitation.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026quot;CVE-2026-55203 - Detect High Volume of HAProxy 5xx Errors\u0026quot; to monitor for unusual spikes in server-side errors that could signal instability or routing issues caused by exploitation.\u003c/li\u003e\n\u003cli\u003eEnable comprehensive logging for HAProxy and its FastCGI backends, including detailed error messages, to facilitate investigation.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-06-18T17:23:08Z","date_published":"2026-06-18T17:23:08Z","id":"https://feed.craftedsignal.io/briefs/2026-06-cve-2026-55203-haproxy-integer-overflow/","summary":"An integer overflow vulnerability (CVE-2026-55203) in HAProxy through version 3.4.0 allows malicious FastCGI backends to desynchronize the FCGI framing parser, leading to request routing errors, response smuggling, or memory safety issues.","title":"CVE-2026-55203 HAProxy Integer Overflow in FastCGI Handling","url":"https://feed.craftedsignal.io/briefs/2026-06-cve-2026-55203-haproxy-integer-overflow/"}],"language":"en","title":"CraftedSignal Threat Feed - Fastcgi","version":"https://jsonfeed.org/version/1.1"}