GitHub Advisoryadvisory · Packagist
GHSA-qc95-4862-92fh Symfony has an HtmlSanitizer allowLinkHosts() / allowMediaHosts() Bypass via URL-Parser Differentials and <area> Misclassification
MEDIUM
Official page ↗
- Aliases
- CVE-2026-45066
- Ecosystem
- Packagist
- Packages
- symfony/html-sanitizer, symfony/symfony
- Severity
- Moderate
- Weaknesses
- CWE-184, CWE-436
- Reviewed
- 2026-05-27
Affected packages
• Packagist symfony/html-sanitizer: >= 6.1.0, < 6.4.40 → fixed in 6.4.40
• Packagist symfony/html-sanitizer: >= 7.0.0, < 7.4.12 → fixed in 7.4.12
• Packagist symfony/html-sanitizer: >= 8.0.0, < 8.0.12 → fixed in 8.0.12
• Packagist symfony/symfony: >= 6.1.0, < 6.4.40 → fixed in 6.4.40
• Packagist symfony/symfony: >= 7.0.0, < 7.4.12 → fixed in 7.4.12
• Packagist symfony/symfony: >= 8.0.0, < 8.0.12 → fixed in 8.0.12
Description
Description
`symfony/html-sanitizer` lets applications sanitise untrusted HTML. The configuration methods `allowLinkHosts([...])` and `allowLinkSchemes([...])` are intended to restrict `` targets to an allowlist of hosts/schemes; `allowMediaHosts()` / `allowMediaSchemes()` do the same for `` etc.
Three distinct bypasses allow a content author to smuggle off-allowlist URLs past these checks. First, `UrlSanitizer::parse()` parses the input following RFC-3986, while browsers follow the WHATWG URL Standard which normalises `\` to `/` before parsing the authority of "special" schemes; so an input like `https://evil\@trusted.com/` parses with host `trusted.com` server-side but navigates to `https://evil/` in the browser. Second, WHATWG collapses any run of `/` after the scheme into `//`, while RFC-3986 does not; so `https:/evil.com/` and `https:///evil.com/` parse as host-less (skipping the host allowlist) but resolve to `evil.com` in the browser. Third, `UrlAttributeSanitizer` checks `'a' === $element` to route to the link policy and falls through to the media policy otherwise, but `` is a navigable hyperlink equivalent to ``; so `` was sanitised against the media policy (which typically allows `data:` and may have no host allowlist), bypassing `allowLinkHosts()` / `allowLinkSchemes()` entirely.
Resolution
`UrlSanitizer::sanitize()` now rejects URLs that contain a backslash or that use a special scheme (`http`, `https`, `ftp`, `ws`, `wss`) followed by a single slash or three slashes before parsing, eliminating the parser-differential bypasses. `UrlAttributeSanitizer` now applies the link policy to both `` and `` elements.
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.
Related
Alias · CVE (1)
- CVE-2026-45066 Symfony is a PHP framework for web and console applications and a set of reusable PHP components. vulnerability
References
- https://github.com/symfony/symfony/security/advisories/GHSA-qc95-4862-92fh web
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/html-sanitizer/CVE-2026-45066.yaml web
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2026-45066.yaml web
- https://github.com/symfony/symfony package
- https://symfony.com/cve-2026-45066 web