GHSA-x6g4-fwcc-jj8w
Fix: symfony/symfony@eea5fd7GHSA-x6g4-fwcc-jj8w is a XML External Entity (XXE) vulnerability in symfony/dom-crawler. O3 Security confirms whether GHSA-x6g4-fwcc-jj8w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Symfony has XXE (Local File Disclosure) in DomCrawler::addXmlContent() via validateOnParse = true
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-x6g4-fwcc-jj8w.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
symfony/dom-crawler🐘symfony/symfony🐘symfony/dom-crawler🐘symfony/dom-crawler🐘symfony/dom-crawler🐘symfony/symfony🐘symfony/symfony🐘symfony/symfonyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Description
symfony/dom-crawler provides the Crawler class for navigating HTML/XML documents with CSS/XPath selectors; symfony/browser-kit's HttpBrowser uses it to parse fetched pages.
Crawler::addXmlContent() sets DOMDocument::$validateOnParse = true before calling loadXML(). Setting validateOnParse re-enables libxml's DTD subset processing, including external entity resolution, even though LIBXML_NONET is passed. LIBXML_NONET blocks network fetches but not file:// entities. An attacker-supplied XML document with a SYSTEM "file:///etc/passwd" entity is therefore expanded.
Resolution
The Crawler::addXmlContent method does not set the validateOnParse flag anymore.
The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and providing the fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/dom-crawler | all versions | 5.4.52 |
| 🐘Packagist | symfony/symfony | all versions | 5.4.52 |
| 🐘Packagist | symfony/dom-crawler | ≥ 6.0.0&&< 6.4.40 | 6.4.40 |
| 🐘Packagist | symfony/dom-crawler | ≥ 7.0.0&&< 7.4.12 | 7.4.12 |
| 🐘Packagist | symfony/dom-crawler | ≥ 8.0.0&&< 8.0.12 | 8.0.12 |
| 🐘Packagist | symfony/symfony | ≥ 6.0.0&&< 6.4.40 | 6.4.40 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/dom-crawler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/dom-crawler to 5.4.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x6g4-fwcc-jj8w 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 pinpoints whether GHSA-x6g4-fwcc-jj8w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-x6g4-fwcc-jj8w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x6g4-fwcc-jj8w in your dependencies?
O3 detects GHSA-x6g4-fwcc-jj8w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.