https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 01:21:52 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-349573 EUVD-2026-349573 https://cve.radiocsirt.org/vuln/euvd-2026-349573 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31842 <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer function uses strcmp to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive.</p> <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer function uses strcmp to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-31842 https://cve.radiocsirt.org/vuln/ghsa-mh87-c4c3-cgwf <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer() function uses strcmp() to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive. By sending a request with Transfer-Encoding: Chunked, an unauthenticated remote attacker can cause Tinyproxy to misinterpret the request as having no body. In this state, Tinyproxy sets content_length.client to -1, skips pull_client_data_chunked(), forwards request headers upstream, and transitions into relay_connection() raw TCP forwarding while unread body data remains buffered. This leads to inconsistent request state between Tinyproxy and backend servers. RFC-compliant backends (e.g., Node.js, Nginx) will continue waiting for chunked body data, causing connections to hang indefinitely. This behavior enables application-level denial of service through backend worker exhaustion. Additionally, in deployments where Tinyproxy is used for request-body inspection, filtering, or security enforcement, the unread body may be forwarded without proper inspection, resulting in potential security control bypass.</p> <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer() function uses strcmp() to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive. By sending a request with Transfer-Encoding: Chunked, an unauthenticated remote attacker can cause Tinyproxy to misinterpret the request as having no body. In this state, Tinyproxy sets content_length.client to -1, skips pull_client_data_chunked(), forwards request headers upstream, and transitions into relay_connection() raw TCP forwarding while unread body data remains buffered. This leads to inconsistent request state between Tinyproxy and backend servers. RFC-compliant backends (e.g., Node.js, Nginx) will continue waiting for chunked body data, causing connections to hang indefinitely. This behavior enables application-level denial of service through backend worker exhaustion. Additionally, in deployments where Tinyproxy is used for request-body inspection, filtering, or security enforcement, the unread body may be forwarded without proper inspection, resulting in potential security control bypass.</p> https://cve.radiocsirt.org/vuln/ghsa-mh87-c4c3-cgwf https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31842 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: tinyproxy, Ubuntu:Pro:16.04:LTS: tinyproxy, Ubuntu:Pro:18.04:LTS: tinyproxy, Ubuntu:20.04:LTS: tinyproxy, Ubuntu:Pro:22.04:LTS: tinyproxy, Ubuntu:24.04:LTS: tinyproxy, Ubuntu:25.10: tinyproxy, Ubuntu:26.04:LTS: tinyproxy</p> <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer function uses strcmp to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: tinyproxy, Ubuntu:Pro:16.04:LTS: tinyproxy, Ubuntu:Pro:18.04:LTS: tinyproxy, Ubuntu:20.04:LTS: tinyproxy, Ubuntu:Pro:22.04:LTS: tinyproxy, Ubuntu:24.04:LTS: tinyproxy, Ubuntu:25.10: tinyproxy, Ubuntu:26.04:LTS: tinyproxy</p> <p>Tinyproxy through 1.11.3 is vulnerable to HTTP request parsing desynchronization due to a case-sensitive comparison of the Transfer-Encoding header in src/reqs.c. The is_chunked_transfer function uses strcmp to compare the header value against &#34;chunked&#34;, even though RFC 7230 specifies that transfer-coding names are case-insensitive.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31842 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0999 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Tinyproxy ausnutzen, um einen Denial of Service Angriff durchzuführen oder Sicherheitsmaßnahmen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Tinyproxy ausnutzen, um einen Denial of Service Angriff durchzuführen oder Sicherheitsmaßnahmen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0999