Open
Conversation
waisingyiu
added
the
maintenance
waisingyiu
force-pushed
the
wsy/fix-fast-xml-parser-vulnerability
branch
from
3c0a4b9 to
a89bf97
Compare
waisingyiu
changed the title
waisingyiu
force-pushed
the
wsy/fix-fast-xml-parser-vulnerability
branch
from
a89bf97 to
a162695
Compare
jonathonherbert
approved these changes
Feb 12, 2026
liamness
reviewed
Feb 12, 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
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.
What does this change?
Our dependency vulnerability dashboard raised a high-severity vulnerability in the fast-xml-parser which is being used by Typerighter.
This dependency is a transitive dependency from GuCDK in the cdk script.
The pull request bumps the GuCDK to the latest version (v62.3.2) which pulls a more recent version of
faxt-xml-parser(v5.3.4) that fixes the vulnerability. It also bumps the node version above nodejs 18 as required by the new GuCDK.How has this change been tested?
Deploy to CODE and run a smoke test, creating a new rule and running a checker in Composer.
How can we measure success?
Resolve the vulnerability on Typerighter in the dependency vulnerability dashboard.
Have we considered potential risks?
Low risk, as it affects the CDK and it passes the test without generating a new snapshot.