chore(deps): update on-headers to 1.1.0#1524
Merged
Merged
Conversation
Collaborator
|
jennifer-shehane
approved these changes
Aug 22, 2025
|
🎉 This PR is included in version 6.10.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
3 participants
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.
Situation
The following example directories report low severity vulnerabilities CVE-2025-7339 due to their transitive dependency usage of on-headers
< 1.1.0:Check with
npm audit:Check with
pnpm audit:yarn auditshows no issue, however Dependabot reports the vulnerability:Maintainers of the repo vercel/serve are not responding to a related issue / PR that would resolve the vulnerability. These have been open for more than one month.
Change
Pin to on-headers@1.1.0 using the appropriate option according to the package manager being used:
package.jsonoption overrides