Skip to main content
No exploitation reportedFix available

CVE-2026-54387

Tinyproxy - HTTP Request Smuggling via CL/TE Desynchronization

No exploitation reported by the sources we read.

  • Published2026-06-17
  • WeaknessCWE-444

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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. Remote attackers can desynchronize the proxy and backend parser state, allowing injection of arbitrary HTTP requests to the backend to enable cache poisoning, access control bypass, and request hijacking.

Timeline

dates in UTC
  1. 2026-06-1719:48CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As VulnCheck, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-07-14

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • tinyproxyUbuntu:Pro:22.04:LTSall versions · no fixed version listed
  • tinyproxyUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • tinyproxyUbuntu:Pro:16.04:LTSall versions · no fixed version listed
  • tinyproxyUbuntu:Pro:14.04:LTSall versions · no fixed version listed
  • tinyproxyUbuntu:26.10all versions · no fixed version listed
  • tinyproxyUbuntu:26.04:LTSall versions · no fixed version listed
  • tinyproxyUbuntu:25.10all versions · no fixed version listed
  • tinyproxyUbuntu:24.04:LTSall versions · no fixed version listed

6 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-06-17
Last Modified
2026-07-14
NVD status
Deferred
GitHub Advisory
GHSA-9667-7p67-2364

Frequently asked questions

What is CVE-2026-54387?

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. Remote attackers can desynchronize the proxy and backend parser state, allowing injection of arbitrary HTTP requests to the backend to enable cache poisoning, access control bypass, and request hijacking.

Is CVE-2026-54387 actively exploited?

Active exploitation of CVE-2026-54387 has not been confirmed. Its EPSS score was 0.4% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-54387?

CVE-2026-54387 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running tinyproxy? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record