Skip to main content
VulnerabilityPublished

CVE-2026-111755: follow-redirects · Incorrect Regular Expression

Affects follow-redirectsSource CVE Database V5

0

Public exploit available · CVSS 8.2 High : upgrade to 1.16.1 as a priority.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-19.

Patch
Available – fixed in 1.16.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 19 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CISA SSVC: proof of concept public

  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

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 3 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 32 minutes after disclosure

  4. In Threat Radar

    record ingested

    , 7 days after disclosure

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

What to do

Upgrade follow-redirects to 1.16.1.

Affected software

ProductAffectedFixed in
follow-redirectsfollow-redirectsAffected
  • >=1.16.0 <1.16.1
Fixed in
  • 1.16.1

AI-suggested

Upgrade follow-redirects to version 1.16.1 or later, where this issue is fixed. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in follow-redirects versions 1.16.0 to before 1.16.1 allows sensitive headers with certain metacharacters to be forwarded to attacker-controlled redirect targets due to incorrect regular expression escaping. This flaw is fixed in version 1.16.1.

References

Community reviews

Loading reviews…