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

> Attackers can bypass URL sanitization using encoded BiDi marks or Unicode whitespace to create visual spoofing attacks in Symfony applications.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-48760, GHSA-v3wm-qf9p-c549, UBUNTU-CVE-2026-48760

## What is CVE-2026-48760?

CVE-2026-48760 is a medium-severity vulnerability in Sensiolabs Symfony, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information), CWE-1007 (Insufficient Visual Distinction of Homoglyphs Presented to User)

## Which versions are affected by CVE-2026-48760?

12 open source packages ship an affected version, including symfony/html-sanitizer and symfony/symfony. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/html-sanitizer` | Packagist | From 6.1.0 | 6.4.41 |
| `symfony/html-sanitizer` | Packagist | From 6.1.0 | 6.4.41 |
| `symfony/html-sanitizer` | Packagist | From 7.0.0 | 7.4.13 |
| `symfony/html-sanitizer` | Packagist | From 7.0.0 | 7.4.13 |
| `symfony/html-sanitizer` | Packagist | From 8.0.0 | 8.0.13 |
| `symfony/html-sanitizer` | Packagist | From 8.0.0 | 8.0.13 |
| `symfony/symfony` | Packagist | From 6.1.0 | 6.4.41 |
| `symfony/symfony` | Packagist | From 6.1.0 | 6.4.41 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.4.13 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.4.13 |
| `symfony/symfony` | Packagist | From 8.0.0 | 8.0.13 |
| `symfony/symfony` | Packagist | From 8.0.0 | 8.0.13 |

Products: Sensiolabs Symfony.

## How do I fix CVE-2026-48760?

Upgrade symfony/html-sanitizer to a fixed version for your release line: 6.4.41, 7.4.13 or 8.0.13.

## Is CVE-2026-48760 being exploited?

There is no known exploitation of CVE-2026-48760 in the wild and no public exploit code.

## Other vulnerabilities in Sensiolabs Symfony

- [CVE-2019-11325](https://insights.sbomify.com/CVE-2019-11325/): Improper Input Validation in Symfony (critical 9.8)
- [CVE-2017-11365](https://insights.sbomify.com/CVE-2017-11365/): Symfony Incorrect Access Control (critical 9.8)
- [CVE-2019-10913](https://insights.sbomify.com/CVE-2019-10913/): Invalid HTTP method overrides allow possible XSS or other attacks in Symfony (critical 9.8)
- [CVE-2018-11407](https://insights.sbomify.com/CVE-2018-11407/): Symfony Authentication Bypass (critical 9.8)
- [CVE-2016-2403](https://insights.sbomify.com/CVE-2016-2403/): Symfony Authentication Bypass (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48760 and fix it if it is affected.

What it is: CVE-2026-48760 is a medium-severity vulnerability in Sensiolabs Symfony, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48760 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/html-sanitizer (Packagist): affected from 6.1.0; fixed in 6.4.41
- symfony/html-sanitizer (Packagist): affected from 6.1.0; fixed in 6.4.41
- symfony/html-sanitizer (Packagist): affected from 7.0.0; fixed in 7.4.13
- symfony/html-sanitizer (Packagist): affected from 7.0.0; fixed in 7.4.13
- symfony/html-sanitizer (Packagist): affected from 8.0.0; fixed in 8.0.13
- symfony/html-sanitizer (Packagist): affected from 8.0.0; fixed in 8.0.13
- symfony/symfony (Packagist): affected from 6.1.0; fixed in 6.4.41
- symfony/symfony (Packagist): affected from 6.1.0; fixed in 6.4.41
- symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.4.13
- symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.4.13
- symfony/symfony (Packagist): affected from 8.0.0; fixed in 8.0.13
- symfony/symfony (Packagist): affected from 8.0.0; fixed in 8.0.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48760/ (Markdown: https://insights.sbomify.com/CVE-2026-48760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48760
- OSV: https://osv.dev/vulnerability/CVE-2026-48760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48760/
Summaries are generated and may contain mistakes; the official description above is the record.