Is symfony/dom-crawler 8.0 vulnerable?
Composer · 6 releases from 8.0.0 to 8.0.12 · latest symfony/dom-crawler is 8.1.10 · checked 18 Nov 2026
No known advisories in the last release
symfony/dom-crawler 8.0.12, the last 8.0 release, has no known advisories. 1 advisory affects earlier 8.0.x releases, so update to 8.0.12.
composer require symfony/dom-crawler:^8.0.12Is your project on an affected symfony/dom-crawler?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 8.0.x, affecting earlier releases
Symfony has XXE (Local File Disclosure) in DomCrawler::addXmlContent() via validateOnParse = true
- Affected
- <5.4.52 · >=6.0.0 <6.4.40 · >=7.0.0 <7.4.12 · >=8.0.0 <8.0.12
- Fixed in
- 5.4.52, 6.4.40, 7.4.12, 8.0.12
Every symfony/dom-crawler 8.0.x release
Affected: 8.0.0 to 8.0.8. 8.0.12 is not affected. Latest symfony/dom-crawler: 8.1.10.
| Version | Known advisories |
|---|---|
| symfony/dom-crawler 8.0.12 | None |
| symfony/dom-crawler 8.0.8 | CVE-2026-45071 |
| symfony/dom-crawler 8.0.6 | CVE-2026-45071 |
| symfony/dom-crawler 8.0.4 | CVE-2026-45071 |
| symfony/dom-crawler 8.0.1 | CVE-2026-45071 |
| symfony/dom-crawler 8.0.0 | CVE-2026-45071 |
Which of your client projects are still on symfony/dom-crawler 8.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact symfony/dom-crawler version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other symfony/dom-crawler versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.