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 using strtol() without properly validating overflow conditions (e.g., errno == ERANGE). A crafted chunk size such as 0x7fffffffffffffff (LONG_MAX) bypasses the existing validation check (chunklen < 0), leading to a signed integer overflow during arithmetic operations (chunklen + 2). This results in incorrect size calculations, causing the proxy to attempt reading an extremely large amount of request-body data and holding worker connections open indefinitely. An attacker can exploit this behavior to exhaust all available worker slots, preventing new connections from being accepted and causing complete service unavailability. Upstream addressed this issue in commit bb7edc4; however, the latest stable release (1.11.3) remains affected at the time of publication.
CVE-2026-3945
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-30. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
References (5)
- 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2chttps://github.com/tinyproxy/tinyproxy/commit/969852c
- 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2chttps://github.com/tinyproxy/tinyproxy/commit/bb7edc4
- 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2chttps://github.com/tinyproxy/tinyproxy/issues/602
- 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2chttps://github.com/tinyproxy/tinyproxy/pull/603
- 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2chttps://github.com/tinyproxy/tinyproxy/releases
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:17 UTCEG score recompute
- 2026-07-27 14:17 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-3945?
When was CVE-2026-3945 disclosed?
Is CVE-2026-3945 actively exploited?
What is the CVSS score of CVE-2026-3945?
How do I remediate CVE-2026-3945?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-3945
Is Your Infrastructure Affected by CVE-2026-3945?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.