Skip to main content
VulnerabilityPublished

CVE-2026-125371: tinyproxy · Partial String Comparison

Affects tinyproxySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 10 Nov 2026, 00:03 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.14.8
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
tinyproxytinyproxyAffected
  • <=1.11.3
Fixed in–

AI-suggested

Users should check the vendor advisory or official Tinyproxy sources for updates or patches. Until a fix is applied, consider restricting access to trusted networks or disabling proxy services if feasible.

Description

Tinyproxy versions up to 1.11.3 have an access control bypass vulnerability due to improper partial string comparison in hostname ACL processing. This flaw allows attackers controlling the PTR record of their source IP to bypass deny-by-default access controls by matching trailing hostname characters incorrectly.

References

Community reviews

Loading reviews…