fix: bump fast-xml-parser from 5.7.0 to ~5.7.2 (entity regression)#135
Merged
Conversation
Version 5.7.0 has a regression in EntityReplacer that rejects valid numeric character references like 
, breaking AWS SDK XML response parsing. Specifically, @aws-sdk/core's parseXmlBody crashes when parsing responses from STS:GetCallerIdentity, which is called by @backstage/integration-aws-node when AWS plugins resolve credentials. 5.7.2 (released 2026-04-24) explicitly fixed this with "Allowed numerical external entities for backward compatibility". Using ~5.7.2 (tilde) instead of ^5.7.2 (caret) to stay within 5.7.x patches — 5.8.0 added xml-naming DOCTYPE validation that could break consumers that send non-standard XML. Confirmed at runtime via Sankhya demo instance: aws-ecs plugin failed with 500 on the entity-services endpoint until this was fixed via workaround. This pin fixes the root cause for all AWS-using plugins. The 5.7.0 pin was introduced in #104 (security fix bot) on 2026-04-28, which narrowed an earlier ^5.3.8 range to an exact version 4 days after the upstream fix was published. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Why
The pin
"fast-xml-parser": "5.7.0"inresolutionshas a runtime regression that breaks AWS SDK XML response parsing.Version 5.7.0 introduced a stricter
EntityReplacerthat rejects valid numeric character references like
with:This breaks
@aws-sdk/core'sparseXmlBody, which crashes when handling responses fromSTS:GetCallerIdentity. That call is made by@backstage/integration-aws-nodewhenever AWS plugins resolve credentials — so every AWS-using plugin (e.g.aws-ecs) goes down.Confirmed at runtime on the Sankhya demo instance: the
aws-ecsplugin returned 500 on the entity-services endpoint until this was patched via workaround. This PR fixes the root cause for all AWS-using plugins.Upstream fixed it in 5.7.2 (released 2026-04-24): "Allowed numerical external entities for backward compatibility".
The 5.7.0 pin was introduced in #104 (security-fix automation) on 2026-04-28, which narrowed an existing
^5.3.8caret range to an exact5.7.0— 4 days after the upstream fix was published, but the bot didn't pick it up.What changes
package.json:"fast-xml-parser": "5.7.0"->"fast-xml-parser": "~5.7.2"insideresolutions.yarn.lock: regenerated byyarn install. Resolves to5.7.3(latest in 5.7.x). Transitivefast-xml-builderbumps from^1.1.5to^1.1.7. No other entries change.Why tilde, not caret
~5.7.2keeps us within 5.7.x patches only.5.8.0added DOCTYPE entity validation viaxml-namingthat is potentially breaking for consumers that send non-standard XML — we don't want auto-upgrade into it.Testing notes
yarn installcompleted cleanly (with only the existing peer-dependency warnings that already exist onmain).yarn.lockdiff is minimal: just thefast-xml-parserentry + itsfast-xml-buildertransitive bump. No unrelated churn.References