CVE-2026-48760: Symfony: HtmlSanitizer URL Parser Deny Gates Underinclusive: Percent-Encoded BiDi Marks and Unicode Whitespace Bypass Visual-Spoofing Defense

Published Jun 15, 2026
·
Updated

Description

Symfony\Component\HtmlSanitizer\TextSanitizer\UrlSanitizer::parse() rejects URLs containing raw Unicode explicit-direction BiDi formatting characters (U+202A–U+202E, U+2066–U+2069) as a defense against visual-spoofing of the rendered href. The check covers only the raw UTF-8 forms of those code points: the percent-encoded forms (%E2%80%AE for U+202E, %E2%81%A6 for U+2066, etc.) are not matched by the deny regex, survive league/uri's parse/build cycle, and are re-emitted unchanged in the sanitized URL. Any downstream consumer that decodes the link before display — phishing-detection filters that compare urldecode($href) against a domain allow-list, audit-log dashboards that show a decoded form for readability, hover-tooltip previews, federated/syndicated content where the decoder lives on the consuming side — restores the BiDi character and the visual spoof that the original defense was filed to prevent.

The same UrlSanitizer::parse() carries an ASCII-only /\s/ whitespace check (no /u modifier) intended as a backstop against malformed URLs. Without the /u modifier, PCRE's \s matches only ASCII whitespace, so Unicode whitespace characters — NBSP (U+00A0), the zero-width no-break space / BOM (U+FEFF), line/paragraph separators (U+2028, U+2029), ogham space (U+1680), the U+2000–U+200A en/em quad family, narrow / medium / ideographic spaces (U+202F, U+205F, U+3000) and NEL (U+0085) — pass through unchanged in both raw and percent-encoded forms. In hostname positions they enable lookalike spoofs (example<NBSP>.com); in path/query/fragment they enable allow-list drift when a downstream consumer strips whitespace before comparison.

Resolution

UrlSanitizer::parse() now denies BiDi formatting marks together with Unicode whitespace and the zero-width no-break space, in both the raw input and the percent-decoded form of each parsed URL component (user, pass, host, path, query, fragment). ASCII space remains tolerated in path/query/fragment via the existing percent-encoding step.

The patches for this issue are available here for branch 6.4 (and forward-ported to 7.4, 8.0 and 8.1).

Credits

Symfony would like to thank Scott Arciszewski (Trail of Bits) for reporting the issue and Nicolas Grekas for providing the fix.

Other sources

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 6.1.0 until 6.4.41, 7.4.13, and 8.0.13, UrlSanitizer::parse() rejected raw BiDi formatting characters but not percent-encoded forms and used an ASCII-only whitespace check, allowing sanitized URLs to retain visual-spoofing characters that downstream consumers could decode or display. This issue is fixed in versions 6.4.41, 7.4.13, and 8.0.13.

MITRE

Affected Software

9 affected componentsFixes available
composer/symfony/symfony>=8.0.0<8.0.13
8.0.13
composer/symfony/symfony>=7.0.0<7.4.13
7.4.13
composer/symfony/symfony>=6.1.0<6.4.41
6.4.41
composer/symfony/html-sanitizer>=8.0.0<8.0.13
8.0.13
composer/symfony/html-sanitizer>=7.0.0<7.4.13
7.4.13
composer/symfony/html-sanitizer>=6.1.0<6.4.41
6.4.41
SensioLabs Symfony>=6.1.0<6.4.41
SensioLabs Symfony>=7.0.0<7.4.13
SensioLabs Symfony>=8.0.0<8.0.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 8.0.13
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 7.4.13
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 6.4.41
  4. Upgrade

    Upgrade composer/symfony/html-sanitizer to a version that resolves this vulnerability.

    Fixed in 8.0.13
  5. Upgrade

    Upgrade composer/symfony/html-sanitizer to a version that resolves this vulnerability.

    Fixed in 7.4.13
  6. Upgrade

    Upgrade composer/symfony/html-sanitizer to a version that resolves this vulnerability.

    Fixed in 6.4.41
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.4.41
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 7.4.13
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.13
  10. Upgrade

    Upgrade Symfony HtmlSanitizer UrlSanitizer deny gates underinclusive: percent-encoded BiDi marks and Unicode whitespace bypass visual-spoofing defense to a version that resolves this vulnerability.

    Patch b21a626fd90f5c12d2db432c629eed3e780ba2f8
  11. Configuration

    Update/patch UrlSanitizer::parse() so it rejects percent-encoded BiDi formatting marks and Unicode whitespace (including U+00A0 NBSP and U+FEFF zero-width no-break space) in both raw and percent-decoded forms for user/pass/host/path/query/fragment.

    Symfony\Component\HtmlSanitizer\TextSanitizer\UrlSanitizer::parse() BiDi/Unicode whitespace denial logic = deny BiDi formatting marks together with Unicode whitespace and the zero-width no-break space; apply to both raw input and percent-decoded form of parsed URL components (user, pass, host, path, query, fragment)

Event History

Jun 15, 2026
Advisory Published
via GitHub·05:32 PM
Data Sourced
via GitHub·05:32 PM
DescriptionWeaknessAffected Software
Jul 14, 2026
CVE Published
via MITRE·07:11 PM
Data Sourced
via MITRE·07:11 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48760?

The severity of CVE-2026-48760 is rated as low risk with a risk score of 33.

2

How do I fix CVE-2026-48760?

To fix CVE-2026-48760, ensure you update your Symfony packages to the latest version where this vulnerability has been addressed.

3

What software is affected by CVE-2026-48760?

CVE-2026-48760 affects Symfony components specifically within the composer/symfony/symfony and composer/symfony/html-sanitizer packages.

4

What issue does CVE-2026-48760 address?

CVE-2026-48760 addresses a vulnerability in the UrlSanitizer::parse() method that may allow visual spoofing through raw Unicode explicit-direction BiDi formatting characters.

5

When was CVE-2026-48760 published?

CVE-2026-48760 was published on June 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203