Clarify sanitize-html affected version range - #8961
Open
pacocartones wants to merge 1 commit into
Open
Conversation
github-actions
Bot
changed the base branch from
main
to
pacocartones/advisory-improvement-8961
August 3, 2026 11:52
pacocartones
marked this pull request as ready for review
August 3, 2026 12:14
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
1 participant
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.
Summary
Clarify the human-readable affected-version statement for GHSA-vccv-cmxp-4j9h.
The advisory's structured npm range already records versions
>= 1.18.0, < 2.17.5, with2.17.4as the last known affected version. This change makes the prose match that existing metadata and names2.17.5as the first patched release.Evidence
1.18.0, fixed in2.17.5.No package, severity, CWE, CVSS, or machine-readable range metadata is changed.