CVE-2026-54387Disclosure

LOW

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

0.5/ 10 priority

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-06-17: 2Patch / Workaround · 2026-06-17: 1Technical Details · 2026-06-17: 206-17
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-54387 HTTP Request Smuggling in Tinyproxy Through 1.11.3 via Header Desynchronization https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-54387

    Post summary

    The text announces the discovery of a new HTTP request smuggling vulnerability (CVE-2026-54387) affecting Tinyproxy up to version 1.11.3, describing its technical nature without providing a PoC, exploit, or mitigation.

    0000052
    4.0K followersView on X
  • CVE@CVEnew
    Disclosure

    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 t… https://www.cve.org/CVERecord?id=CVE-2026-54387

    Post summary

    Tinyproxy up to version 1.11.3 is vulnerable due to conflicting Content‑Length and Transfer‑Encoding: chunked headers being forwarded verbatim; the issue was fixed in commit ff45d3b.

    00000128
    57.6K followersView on X

Explore more