Bleach: URI sanitization allows disallowed URI schemes with Unicode > U+00A0 in output
Published 16 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected bleach?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <6.4.0
- Fixed in
- 6.4.0
pip install 'bleach>=6.4.0'Details
Impact
A possible XSS bypass affects users calling bleach.clean with all of:
ain the allowed tagshrefin allowed attributes
The bleach.clean sanitizer outputs URIs containing disallowed scheme patterns that it should be stripping. However, because the inserted Unicode characters make the scheme invalid per RFC 3986, modern browsers do not execute these as javascript: URIs. The practical security impact is limited to:
- Bleach's output contains URI values that violate the caller's protocol allowlist, breaking the sanitizer's contract.
- If a downstream system performs its own Unicode normalization on bleach's output (stripping invisible characters before rendering), the javascript: scheme could become valid. This is a non-standard processing chain but represents a theoretical secondary risk.
This is not a direct XSS vulnerability.
Python code example from reporter with Bleach v6.3.0 and Python 3.13:
import bleach
payload1 = '<a href="javascript\u200b:alert(document.cookie)">Click me</a>'
result1 = bleach.clean(payload1)
print(f"(ZWSP): {repr(result1)}")Output:
(ZWSP): '<a href="javascript\u200b:alert(document.cookie)">Click me</a>'
Patches
Users should upgrade to Bleach 6.4.0.
Workarounds
Pre-process content removing non-ASCII characters from URI schemes before sanitizing with bleach.clean.
A strong Content-Security-Policy without unsafe-inline and unsafe-eval script-srcs will also help mitigate the risk.
References
- https://bugzilla.mozilla.org/show_bug.cgi?id=2023812
- RFC 3986, Section 3.1 (URI Scheme syntax): scheme characters are restricted to ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )
Reported by
Reported by codeant from CodeAnt AI.
Is GHSA-8rfp-98v4-mmr6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected bleach, and gives you the command that fixes it.
More advisories for bleach
- MediumGHSA-gj48-438w-jh9vBleach clean() / Cleaner() fails to sanitize dangerous URI schemes in allowed formaction attributes · 16 Jun 2026
- MediumGHSA-g75f-g53v-794xBleach linkify(parse_email=True) CPU exhaustion via unbounded email regex scanning · 16 Jun 2026
- MediumCVE-2021-23980Cross-site scripting in Bleach · 2 Feb 2021
- HighCVE-2020-6817regular expression denial-of-service (ReDoS) in Bleach · 30 Mar 2020
- MediumCVE-2020-6816Bleach vulnerable to mutation XSS via whitelisted math or svg and raw tag · 24 Mar 2020
- MediumCVE-2020-6802XSS in Bleach when noscript and raw tag whitelisted · 24 Feb 2020
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.