Skip to content

[Snyk] Upgrade fast-xml-parser from 5.3.6 to 5.5.3 - #2

Open
snyk-io[bot] wants to merge 1 commit into
mainfrom
snyk-upgrade-6c5e4fb9247cad6b0ff9005ebb1ba8a2
Open

[Snyk] Upgrade fast-xml-parser from 5.3.6 to 5.5.3#2
snyk-io[bot] wants to merge 1 commit into
mainfrom
snyk-upgrade-6c5e4fb9247cad6b0ff9005ebb1ba8a2

Conversation

@snyk-io

@snyk-io snyk-io Bot commented Apr 1, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade fast-xml-parser from 5.3.6 to 5.5.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 10 versions ahead of your current version.

  • The recommended version was released 21 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Buffer Overflow
SNYK-JS-FASTXMLPARSER-15353391
49 No Known Exploit

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.

Release notes
Package name: fast-xml-parser
  • 5.5.3 - 2026-03-11

    upgrade builder

  • 5.5.2 - 2026-03-11

    Full Changelog: v5.5.1...v5.5.2

  • 5.5.1 - 2026-03-10
    • support path-expression-matcher
    • fix: stopNode should not be parsed
    • performance improvement for stopNode checking
  • 5.5.0 - 2026-03-10

    integrate path-expression-matcher

  • 5.4.2 - 2026-03-03

    support maxEntityCount

  • 5.4.1 - 2026-02-25

    fix tag content for unpaired tag

  • 5.4.0 - 2026-02-25

    XML Builder was the part of fast-xml-parser for years. But considering that any bug in builder may false-alarm the users who are only using parser and vice-versa, we have decided to split it into a separate package.

    Migration

    To migrate to fast-xml-builder;

    From

    import { XMLBuilder } from "fast-xml-parser";

    To

    import  XMLBuilder  from "fast-xml-builder";

    XMLBuilder will be removed from current package in any next major version of this library. So better to migrate.

  • 5.3.9 - 2026-02-25

    Full Changelog: v5.3.9...v5.3.9

  • 5.3.8 - 2026-02-25
  • 5.3.7 - 2026-02-20
  • 5.3.6 - 2026-02-14
from fast-xml-parser GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade fast-xml-parser from 5.3.6 to 5.5.3.

See this package in npm:
fast-xml-parser

See this project in Snyk:
https://app.snyk.io/org/test-cAX4cfyGGwqSqgMRHFEhFe/project/5e8ff93d-0599-4892-a241-c438cc1ca3d8?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
@snyk-io

snyk-io Bot commented Apr 1, 2026

Copy link
Copy Markdown
Author

Merge Risk: Medium

This upgrade from version 5.3.6 to 5.5.3 of fast-xml-parser includes several new features, dependency updates, and behavioral bug fixes that could impact existing applications.

Key Changes:

  • Behavioral Fix for Unpaired Tags: Version 5.4.1 fixes an issue where an unpaired tag could incorrectly contain content. After this update, unpaired tags will no longer have content, which may affect logic that relied on the previous behavior.
  • Behavioral Fix for Stop Nodes: Version 5.5.0 fixes an issue where stopNode elements were being parsed. They will now be correctly ignored.
  • Builder Migration: Version 5.4.0 migrates the XML builder functionality to a separate fast-xml-builder package. While the builder is still available in this version, it is now deprecated and will be removed in a future major version.

Recommendation:
These are behavioral changes that require verification. It is recommended to test your XML parsing logic, especially if you handle unpaired tags or stop nodes, to ensure compatibility with the updated behavior.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants