chore(deps): update dependency follow-redirects to v1.16.0 [security]#328
Merged
renovate[bot] merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.15.11→1.16.0GitHub Vulnerability Alerts
GHSA-r4q5-vmmm-2653
Summary
When an HTTP request follows a cross-domain redirect (301/302/307/308),
follow-redirectsonly stripsauthorization,proxy-authorization, andcookieheaders (matched by regex at index.js:469-476). Any custom authentication header (e.g.,X-API-Key,X-Auth-Token,Api-Key,Token) is forwarded verbatim to the redirect target.Since
follow-redirectsis the redirect-handling dependency for axios (105K+ stars), this vulnerability affects the entire axios ecosystem.Affected Code
index.js, lines 469-476:The regex only matches
authorization,proxy-authorization, andcookie. Custom headers likeX-API-Keyare not matched.Attack Scenario
headers: { 'X-API-Key': 'sk-live-secret123' }302 Location: https://evil.com/stealX-API-Key: sk-live-secret123toevil.comImpact
Any custom auth header set via axios leaks on cross-domain redirect. Extremely common pattern. Affects all axios users in Node.js.
Suggested Fix
Add a
sensitiveHeadersoption that users can extend, or strip ALL non-standard headers on cross-domain redirect.Disclosure
Source code review, manually verified. Found 2026-03-20.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NRelease Notes
follow-redirects/follow-redirects (follow-redirects)
v1.16.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.