Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45064 medium CVSS 6.1

Vulnerability in symfony/html-sanitizer (CVE-2026-45064)

Summary

Vulnerability in symfony/html-sanitizer (CVE-2026-45064). Risk of unauthorized operations or information disclosure. Exploitable via HtmlSanitizer. Mitigation: upgrade to 8.0.12 or later.

Original description

The description as published by the source.

Description

Symfony\Component\HtmlSanitizer\TextSanitizer\UrlSanitizer::parse() (used by UrlSanitizer::sanitize() and therefore by every HtmlSanitizer config that allows links or media) accepts URLs that contain Unicode explicit-direction BiDi formatting characters: U+202A–U+202E (LRE / RLE / PDF / LRO / RLO) and U+2066–U+2069 (LRI / RLI / FSI / PDI). These characters are passed through unchanged into the href / src attributes produced by HtmlSanitizer. When the resulting HTML is rendered in a browser, the override characters reverse or alter the visual ordering of the URL text, so the displayed link can differ arbitrarily from the actual destination: a classic visual-spoofing / phishing primitive against viewers of sanitized content.

Resolution

UrlSanitizer::parse() now rejects URLs containing the explicit-direction BiDi formatting code points (U+202A–U+202E, U+2066–U+2069) before invoking the underlying URL parser. As an unrelated companion fix in the same patch, spaces inside path/query/fragment are now percent-encoded rather than rejected outright, while spaces in the scheme/authority remain rejected by the post-encoding whitespace check.

The patch for this issue is available here for branch 5.4.

Credits

Symfony would like to thank Himanshu Anand for reporting the issue and Nicolas Grekas for providing the fix.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45064 has been found in symfony/html-sanitizer.
Attackers can target a specific entry point like HtmlSanitizer over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade symfony/html-sanitizer to 8.0.12 or later.
If unsure, ask your IT team or search "symfony/html-sanitizer CVE-2026-45064" on the vendor's site.

CVE-2026-45064 (symfony/html-sanitizer) — CWE-451 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: HtmlSanitizer / href / src
Patched: 8.0.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-451) exists in symfony/html-sanitizer. Attackers reach the vulnerable code path via HtmlSanitizer without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of symfony/html-sanitizer. Attack surface: HtmlSanitizer / href / src.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.0.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'symfony/html-sanitizer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'symfony/html-sanitizer' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で symfony/html-sanitizer を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade symfony/html-sanitizer to 8.0.12

    ステージング環境で 8.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer symfony/html-sanitizer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.12"}]}]
composer symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.12"}]}]
Packagist symfony/html-sanitizer
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.12"}]}]
Packagist symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.12"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details