Correct affected range/fixed version for GHSA-5jp3-wp5v-5363 (CVE-2024-6706)#8778
Open
Classic298 wants to merge 1 commit into
Open
Conversation
github-actions
Bot
changed the base branch from
main
to
Classic298/advisory-improvement-8778
July 22, 2026 21:07
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.
Corrects the affected range for GHSA-5jp3-wp5v-5363 (CVE-2024-6706).
The record currently ends the range at
last_affected: 0.1.105, which understates the affected versions. The stored/rendered XSS (assistant output rendered via{@html token.text}with no sanitizer) was fixed in v0.3.14 by commit 5a6ece951 ("refac: enhanced response content sanitisation"), which introduced DOMPurify and wrapped the html-token branch inDOMPurify.sanitize(...). The raw render is present through v0.3.13, so the affected range extends to 0.3.13 and the fix first ships in 0.3.14.This PR replaces
last_affected: 0.1.105withfixed: 0.3.14so the range covers every affected release and terminates at the first fixed release.