← Back to results
Vulnerability record · public intelligence
CVE-2023-34104
HIGH

fast-xml-parser vulnerable to Regex Injection via Doctype Entities

Published Jun 6, 2023 · Updated Oct 23, 2026 · Also known as GHSA-6w63-h3fj-q4vw

Severity · CVSSHIGH · 7.5
Known exploitationNot listed
EPSS / likelihood1.13%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

fast-xml-parser vulnerable to Regex Injection via Doctype Entities

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

"fast-xml-parser" allows special characters in entity names, which are not escaped or sanitized. Since the entity name is used for creating a regex for searching and replacing entities in the XML body, an attacker can abuse it for DoS attacks. By crafting an entity name that results in an intentionally bad performing regex and utilizing it in the entity replacement step of the parser, this can cause the parser to stall for an indefinite amount of time.

Potential impact

"fast-xml-parser" allows special characters in entity names, which are not escaped or sanitized. Since the entity name is used for creating a regex for searching and replacing entities in the XML body, an attacker can abuse it for DoS attacks. By crafting an entity name that results in an intentionally bad performing regex and utilizing it in the entity replacement step of the parser, this can cause the parser to stall for an indefinite amount of time.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
10%
Aliases
GHSA-6w63-h3fj-q4vw

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Patch commit ↗

Record history

Published Jun 6, 2023 · Last refreshed Oct 23, 2026