Summary
Dennis Sepede discovered that follow-redirects did not properly remove
custom authentication headers when following cross-domain redirects. An
attacker could possibly use this issue to obtain sensitive authentication
information, resulting in credential disclosure.
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 18.04 LTS Pro:18.04:LTS | node-follow-redirects | 1.2.4-1ubuntu0.18.04.1~esm2 |
| Ubuntu · Pro 20.04 LTS Pro:20.04:LTS | node-follow-redirects | 1.2.4-1ubuntu0.20.04.1~esm2 |
| Ubuntu · Pro 22.04 LTS Pro:22.04:LTS | node-follow-redirects | 1.14.9+~1.14.1-1ubuntu0.1~esm2 |
| Ubuntu · Pro 24.04 LTS Pro:24.04:LTS | node-follow-redirects | 1.15.6+~1.14.4-1ubuntu0.1~esm1 |
| Ubuntu · Pro 26.04 LTS Pro:26.04:LTS | node-follow-redirects | 1.15.11+~1.14.4-1ubuntu0.1~esm1 |
Vulnerabilities 1
-
Medium 6.9
follow-redirects: Custom Authentication Headers Leaked to Cross-Domain Redirect Targets
follow-redirects is an open source, drop-in replacement for Node's `http` and `https` modules that automatically follows redirects. Prior to 1.16.0, when an HTTP request follows a cross-domain redirect (301/302/307/308), follow-redirects only strips authoriza…
References
-
report
https://ubuntu.com/security/CVE-2026-40895