fix(deps): update dependency node-fetch to v2.6.7 [security] - #172
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency node-fetch to v2.6.7 [security]#172renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Author
⚠ Artifact update problemRenovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.jsonFile name: yarn.lock |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
Bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
August 10, 2025 13:08
db0481f to
2645256
Compare
|
Deployment failed with the following error: |
renovate
Bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
November 18, 2025 14:05
2645256 to
d68b8a3
Compare
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/environment-variables |
renovate
Bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
2 times, most recently
from
March 30, 2026 20:52
d68b8a3 to
24ce595
Compare
renovate
Bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
2 times, most recently
from
April 27, 2026 21:22
24ce595 to
e294a49
Compare
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:
2.6.0→2.6.7node-fetch forwards secure headers to untrusted sites
CVE-2022-0235 / GHSA-r683-j2x4-v87g
More information
Details
node-fetch forwards secure headers such as
authorization,www-authenticate,cookie, &cookie2when redirecting to a untrusted site.Severity
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
node-fetch/node-fetch (node-fetch)
v2.6.7Compare Source
Security patch release
Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred
What's Changed
Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7
v2.6.6Compare Source
What's Changed
Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6
v2.6.5Compare Source
v2.6.4Compare Source
v2.6.3Compare Source
v2.6.2Compare Source
fixed main path in package.json
v2.6.1Compare Source
This is an important security release. It is strongly recommended to update as soon as possible.
See CHANGELOG for details.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.