Support unicode characters in the json parser#3142
Merged
Conversation
reta
approved these changes
May 25, 2026
coheigea
added a commit
that referenced
this pull request
May 26, 2026
(cherry picked from commit 4197b3f)
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.
JSON allows you to write any character using a backslash-u escape — for example, \u006e means the letter n. The CXF parser was ignoring these escapes completely and just returning the raw text. So if a JWT contained "alg":"\u006e\u006f\u006e\u0065", CXF's parser would give you the 24-character string \u006e\u006f\u006e\u0065 rather than the 4-character string none. CXF's own algorithm check would look at that ugly literal string, not recognise it as none, and pass it through — while a different, standards-compliant parser further down the chain would decode it correctly and see none, potentially disabling signature verification.