Intel

AIKIDO-2026-154218

follow-redirects is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

CVE-2026-111755Published Oct 7, 2026
October 7, 2026

53

CVE Score

Medium

Exposure of Sensitive Information to an Unauthorized Actor

Are you affected? Scan for Free

TL;DR

The sensitiveHeaders option in follow-redirects lets callers name extra credential headers to strip on cross origin redirects. The library passes each name through escapeRegex and joins them into one case insensitive regular expression, but escapeRegex leaves ^, |, [, {, and } unescaped. A declared header name containing ^ or |, both valid RFC 9110 token characters, produces a pattern that never matches the header, so the application forwards that credential header unchanged to the redirected destination with no error. The fix escapes the remaining regular expression metacharacters in escapeRegex.

How do I fix this?

Upgrade the follow-redirects library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you declare a custom sensitiveHeaders entry whose name contains a regular expression metacharacter such as ^ or |.

Versions

1.16.0 - 1.16.0

Fixed in 1.16.1

Background info

follow-redirects is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 1.16.0 - 1.16.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea