dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-3945

HIGH · 7.5 CVSS v3.1 Published 2026-03-30
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix Moderate confidence

Latest version after 1.11.3 that includes commit bb7edc4 (or 969852c)

  1. 1. Identify the current tinyproxy version installed (e.g., `tinyproxy --version` or check package manager)
  2. 2. Obtain the fixed version of tinyproxy that includes the security patch from commit bb7edc4 (which addresses the integer overflow in chunked transfer encoding parsing)
  3. 3. Update the tinyproxy package through the system package manager (e.g., `apt-get update && apt-get install tinyproxy` for Debian/Ubuntu, or `yum update tinyproxy` for RHEL/CentOS)
  4. 4. If building from source, download the latest source and apply the fix commit: `git clone https://github.com/tinyproxy/tinyproxy.git && cd tinyproxy && git checkout bb7edc4` or `git checkout 969852c`
  5. 5. Rebuild and reinstall tinyproxy from the patched source
  6. 6. Restart the tinyproxy service to apply the update (e.g., `systemctl restart tinyproxy` or `service tinyproxy restart`)
  7. 7. Verify the new version is running and the service is operational
Caveat Minor - this is a security bugfix; upgrading from 1.11.x to a newer stable release should not introduce breaking changes for normal proxy operation

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3945 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data