complete control byte stripping#17957
Open
curious-rabbit wants to merge 1 commit into
Open
Conversation
kasper93
reviewed
May 21, 2026
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
2 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.
The current sanitizer let BS, VT, FF and raw 8-bit C1 bytes (0x80-0x9F) reach the terminal, which a hostile filename or title can use to overwrite or clear output. Allow only HT, LF, CR among C0 and block raw C1, with aUTF-8-aware skip so emoji and other multi-byte characters still pass.
this means on vte terminals (gnome terminal,) xterm and some other terminal emulators the filter can be circumvented and control bytes are interpreted.