p PatchFirst

PatchFirst · Latest vulnerabilities

bleach vulnerabilities

Vulnerabilities published for bleach in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 8

  1. GHSA-gj48-438w-jh9v

    Medium · CVSS 6.1Fix available

    Bleach clean() / Cleaner() fails to sanitize dangerous URI schemes in allowed formaction attributes

    ### Summary Bleach `clean()` / `Cleaner()` fails to sanitize dangerous URI schemes in allowed `formaction` attributes. Bleach applies URI protocol sanitization only to attributes listed in `attr_val_is_uri`. While URI-bearing attributes such as `action`, `href`, `src`, and `poster` are included in that set, `formaction` is not. As a result, if a downstream application explicitly allows `formaction` on submit-capable controls in untrusted HTML, Bleach preserves dangerous values such as `javascript:alert(1)` instead of stripping them. This can lead to **submit-triggered JavaScript execution** in applications that rely on Bleach to sanitize u

    • Update to 6.4.0
    Published Updated
  2. GHSA-g75f-g53v-794x

    Medium · CVSS 4.3No fix published

    Bleach linkify(parse_email=True) CPU exhaustion via unbounded email regex scanning

    ## Summary Bleach 6.3.0 exposes a documented email-linkification path through `bleach.linkify(..., parse_email=True)`. The implementation scans attacker-controlled text with `EMAIL_RE.finditer()` over the full character token and has no length, timeout, or linear prefilter before applying the dot-atom email regex. A non-email payload around 30 KB causes multi-second CPU consumption per request/call, creating a direct availability risk for applications that enable email linkification on user-submitted text. ## Affected Product - Package: `bleach` - Ecosystem: pip - Affected versions: verified in `6.3.0`; exact first affected version not estab

    Published Updated
  3. GHSA-8rfp-98v4-mmr6

    Low · CVSS 0Fix available

    Bleach: URI sanitization allows disallowed URI schemes with Unicode > U+00A0 in output

    ### 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 (stri

    • Update to 6.4.0
    Published Updated
  4. CVE-2021-23980

    Medium · CVSS 6.1EPSS 0.48%Fix available

    CVE-2021-23980

    A mutation XSS affects users calling bleach.clean with all of: svg or math in the allowed tags p or br in allowed tags style, title, noscript, script, textarea, noframes, iframe, or xmp in allowed tags the keyword argument strip_comments=False Note: none of the above tags are in the default allowed tags and strip_comments defaults to True.

    • Update to 3.3.0
    Published Updated
  5. CVE-2020-6817

    High · CVSS 7.5EPSS 0.72%Fix available

    CVE-2020-6817

    bleach.clean behavior parsing style attributes could result in a regular expression denial of service (ReDoS). Calls to bleach.clean with an allowed tag with an allowed style attribute are vulnerable to ReDoS. For example, bleach.clean(..., attributes={'a': ['style']}).

    • Update to 3.1.4
    Published Updated
  6. CVE-2018-7753

    Critical · CVSS 9.8EPSS 2.17%Fix available

    CVE-2018-7753

    An issue was discovered in Bleach 2.1.x before 2.1.3. Attributes that have URI values weren't properly sanitized if the values contained character entities. Using character entities, it was possible to construct a URI value with a scheme that was not allowed that would slide through unsanitized.

    • Update to 2.1.3
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →