How severe is GHSA-gpv5-7x3g-ghjv?

No CVSS score has been assigned to GHSA-gpv5-7x3g-ghjv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gpv5-7x3g-ghjv?

GHSA-gpv5-7x3g-ghjv affects the following packages: fast-xml-parser (npm). Ecosystems affected: npm.

How do I fix GHSA-gpv5-7x3g-ghjv?

Update fast-xml-parser to 4.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gpv5-7x3g-ghjv is resolved across your whole dependency graph.

How do I detect GHSA-gpv5-7x3g-ghjv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-xml-parser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gpv5-7x3g-ghjv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gpv5-7x3g-ghjv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gpv5-7x3g-ghjv can be triaged on real exposure rather than presence alone.

Is GHSA-gpv5-7x3g-ghjv actively exploited in the wild?

No public exploit code has been indexed for GHSA-gpv5-7x3g-ghjv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-gpv5-7x3g-ghjv published, and has it been updated?

GHSA-gpv5-7x3g-ghjv was published on June 15, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-gpv5-7x3g-ghjv — fast-xml-parser

Fix: NaturalIntelligence/fast-xml-parser@9a880b8

GHSA-gpv5-7x3g-ghjv is a security vulnerability in fast-xml-parser. A fix is available for fast-xml-parser — see the affected versions and patch details below.

fast-xml-parser regex vulnerability patch could be improved from a safety perspective

Published

Jun 15, 2023

Updated

Jun 15, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 15, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

fast-xml-parsernpm

56.7Mdownloads / week

Description

Summary

This is a comment on https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-6w63-h3fj-q4vw and the patches fixing it.

Details

The code which validates a name calls the validator: https://github.com/NaturalIntelligence/fast-xml-parser/blob/ecf6016f9b48aec1a921e673158be0773d07283e/src/xmlparser/DocTypeReader.js#L145-L153 This checks for the presence of an invalid character. Such an approach is always risky, as it is so easy to forget to include an invalid character in the list. A safer approach is to validate entity names against the XML specification: https://www.w3.org/TR/xml11/#sec-common-syn - an ENTITY name is a Name:

[4]   NameStartChar ::= ":" | [A-Z] | "_" | [a-z] | [#xC0-#xD6] | [#xD8-#xF6] | [#xF8-#x2FF] | [#x370-#x37D] |
                        [#x37F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] |
                        [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF]
[4a]  NameChar ::= NameStartChar | "-" | "." | [0-9] | #xB7 | [#x0300-#x036F] | [#x203F-#x2040]
[5]   Name ::= NameStartChar (NameChar)*

so the safest way to validate an entity name is to build a regex to represent this expression and check whether the name given matches the regex. (Something along the lines of /^[name start char class][name char class]*$/.) There's probably a nice way to simplify the explicit list rather than typing it out verbatim using Unicode character properties, but I don't know enough to do so.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fast-xml-parser`	≥ 4.2.4&&< 4.2.5	4.2.5`npm install fast-xml-parser@4.2.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-xml-parser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fast-xml-parser to 4.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gpv5-7x3g-ghjv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gpv5-7x3g-ghjv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-gpv5-7x3g-ghjv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary This is a comment on https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-6w63-h3fj-q4vw and the patches fixing it. ### Details The code which validates a name calls the validator: https://github.com/NaturalIntelligence/fast-xml-parser/blob/ecf6016f9b48aec1a921e673158be0773d07283e/src/xmlparser/DocTypeReader.js#L145-L153 This checks for the presence of an invalid character. Such an approach is always risky, as it is so easy to forget to include an invalid character in the list. A safer approach is to validate entity names against the XML specification:

O3 Security · Impact-Aware SCA

Is GHSA-gpv5-7x3g-ghjv in your dependencies?

O3 Security finds GHSA-gpv5-7x3g-ghjv across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works