Skip to content

fix(deps): drop fast-xml-parser pin breaking the S3 deploy#7560

Merged
santicomp2014 merged 1 commit into
mainfrom
vuln-remediation/fix-fast-xml-parser-deploy
Jul 1, 2026
Merged

fix(deps): drop fast-xml-parser pin breaking the S3 deploy#7560
santicomp2014 merged 1 commit into
mainfrom
vuln-remediation/fix-fast-xml-parser-deploy

Conversation

@santicomp2014

Copy link
Copy Markdown
Contributor

Fixes the broken client Release pipeline (release-staging → Deploy to S3, run 28532169799).

#7557 added an unscoped fast-xml-parser: 5.7.0 resolution. @aws-sdk's XML response parser (in scripts/deploy-to-s3.js) chokes on the 
 entity in S3's XML reply with 5.7.0:

Failed to upload S3 package Error: [EntityReplacer] Invalid character '#' in entity name: "#xD"

The S3 upload itself returns HTTP 200 — only parsing the response fails. Deploy isn't part of PR CI, so this passed review and only surfaced post-merge on main, blocking all client deploys.

Why dropping the pin is safe

fast-xml-parser is deploy-tooling only (@aws-sdk, not shipped to the browser). Its CVEs are either in the XMLBuilder (write path — @aws-sdk only parses) or need untrusted XML input (@aws-sdk parses trusted S3 responses). So the finding is LOW and not reachable here. This reverts to 5.2.5 — the @aws-sdk-compatible version that deployed fine before #7557. All 25 other resolutions from #7557 are untouched.

Proper long-term fix: bump @aws-sdk to a version bundling a fixed fast-xml-parser.

🤖 Generated with Claude Code

The fast-xml-parser 5.7.0 resolution added in #7557 broke the client Release
pipeline at 'Deploy to S3': @aws-sdk's XML response parser (fast-xml-parser
5.7.0) rejects the '
' entity in S3's XML reply ([EntityReplacer] Invalid
character '#' in entity name: '#xD'). Deploy isn't in PR CI, so it passed
review and only failed post-merge on main.

fast-xml-parser here is deploy-tooling only (@aws-sdk in scripts/deploy-to-s3.js),
not shipped. Its CVEs are in the XMLBuilder (write path, unused by @aws-sdk) or
need untrusted XML input (@aws-sdk parses trusted S3 responses) -> LOW and not
reachable. Reverting to the @aws-sdk-compatible 5.2.5 restores the working
deploy; the proper long-term fix is bumping @aws-sdk itself.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@santicomp2014 santicomp2014 merged commit ca32603 into main Jul 1, 2026
2 checks passed
@santicomp2014 santicomp2014 deleted the vuln-remediation/fix-fast-xml-parser-deploy branch July 1, 2026 16:46
@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.62%. Comparing base (9bbcf25) to head (7dccbc4).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7560   +/-   ##
=======================================
  Coverage   99.62%   99.62%           
=======================================
  Files         285      285           
  Lines       11971    11971           
  Branches     2920     2920           
=======================================
  Hits        11926    11926           
  Misses         45       45           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

santicomp2014 pushed a commit that referenced this pull request Jul 1, 2026
Reverts the resolutions block to restore the last-known-good build output.
#7557's build-tool pins (serialize-javascript v6->v7 etc.) changed the
generated inline bootstrap script's bytes, so its sha256 no longer matched
the CSP script-src hash allowlist the backend serves -> browser blocked the
inline script -> broken client in production (CSP violation).

Restores package.json + yarn.lock to 6307520 (pre-#7557). Security pins will
be re-applied carefully, excluding the ones that alter build output / CSP hash.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant