GHSA-8rfp-98v4-mmr6: XSS

Published Jun 16, 2026
·
Updated

Impact

A possible XSS bypass affects users calling bleach.clean with all of:

a in the allowed tags href in 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/showbug.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.

Affected Software

1 affected componentFixes available
pip/bleach<=6.3.0
6.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/bleach to a version that resolves this vulnerability.

    Fixed in 6.4.0
  2. Configuration

    Pre-process content to remove non-ASCII (invisible/zero-width) characters from URI schemes before calling bleach.clean.

    pre-processing before bleach.clean remove_non_ascii_from_uri_schemes = true
  3. Compensating control

    Deploy a strong Content-Security-Policy that does not allow 'unsafe-inline' or 'unsafe-eval' in script-src to mitigate risks from potentially malformed javascript: URIs.

Event History

Jun 16, 2026
Advisory Published
via GitHub·02:06 PM
Data Sourced
via GitHub·02:06 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of GHSA-8rfp-98v4-mmr6?

The severity of GHSA-8rfp-98v4-mmr6 is rated at 15.

2

What is the nature of the vulnerability in GHSA-8rfp-98v4-mmr6?

GHSA-8rfp-98v4-mmr6 is an XSS bypass vulnerability in the bleach.clean sanitizer.

3

How does GHSA-8rfp-98v4-mmr6 affect users?

Users calling bleach.clean with specific allowed tags and attributes may experience uncensored disallowed scheme patterns.

4

How do I mitigate GHSA-8rfp-98v4-mmr6?

To mitigate GHSA-8rfp-98v4-mmr6, avoid using disallowed scheme patterns in URIs within bleach.clean.

5

What versions of bleach are affected by GHSA-8rfp-98v4-mmr6?

GHSA-8rfp-98v4-mmr6 affects versions of the bleach library that allow specified tags and attributes in sanitization.

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