CyberSecBulletin

Tinyproxy vulnerabilities

We track 5 vulnerabilities in Tinyproxy products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on June 17, 2026.

5vulnerabilities
3critical
2high
0exploited
8.7average CVSS score

Latest Tinyproxy vulnerabilities

  • 8.2 High severity

    tinyproxy: Authentication Bypass by Spoofing

    CVE-2026-55202Tinyproxy

    Tinyproxy through 1.11.3, fixed in commit 09312a1, fails to properly validate the Host header during stathost detection, allowing unauthenticated attackers to access the stats page by injecting a matching Host header or bypass detection via port manipulation.

  • 9.1 Critical severity

    tinyproxy: Inconsistent Interpretation of HTTP Requests

    CVE-2026-54388Tinyproxy

    Tinyproxy through 1.11.3, fixed in commit 364cdb6, fails to reject requests containing multiple Content-Length headers with differing values, forwarding all duplicate headers to the backend while using the first value to determine how many request body bytes t

  • 9.1 Critical severity

    tinyproxy: Inconsistent Interpretation of HTTP Requests

    CVE-2026-54387Tinyproxy

    Tinyproxy through 1.11.3, fixed in commit ff45d3b, fails to reconcile conflicting Content-Length and Transfer-Encoding: chunked headers, forwarding both verbatim to the backend while using Content-Length to determine how many request body bytes to consume. Rem

  • 7.5 High severity

    tinyproxy: Integer Overflow or Wraparound

    CVE-2026-3945Tinyproxy

    An integer overflow vulnerability in the HTTP chunked transfer encoding parser in tinyproxy up to and including version 1.11.3 allows an unauthenticated remote attacker to cause a denial of service (DoS). The issue occurs because chunk size values are parsed u

  • 9.8 Critical severity

    Tinyproxy: Use After Free

    CVE-2023-49606TinyproxyEPSS 80.9%

    A use-after-free vulnerability exists in the HTTP Connection Headers parsing in Tinyproxy 1.11.1 and Tinyproxy 1.10.0. A specially crafted HTTP header can trigger reuse of previously freed memory, which leads to memory corruption and could lead to remote code