Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-8r9p-f939-6h3c

follow-redirects sensitiveHeaders regex escaping can expose credential headers

CVSS 8.2 HighEPSS 0.0047 · 40th percentile

Published by the GitHub Advisory Database at 20 Oct 2026, 17:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
follow-redirectsnpm>=1.16.0, <1.16.11.16.1
Identifiers
GHSA-8r9p-f939-6h3c · CVE-2026-111755
Weakness (CWE)
CWE-185 · CWE-200
Tags
Published
20 Oct 2026
Updated
20 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: the npm package follow-redirects, versions 1.16.0 up to but not including 1.16.1, in its sensitiveHeaders option. Header names containing "^" or "|" are not escaped correctly when building the filter, so the filter silently fails to strip those headers on cross-origin or protocol-downgrading redirects. An attacker who controls a redirect target could then receive the custom credential header value. Upgrade to follow-redirects 1.16.1, which fixes the issue. The built-in headers (Authorization, Proxy-Authorization, Cookie) are not affected.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0047, the 40th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.