GHSA-c9vm-hv86-f23r: Justhtml Justhtml Includes Multiple Security Fixes Vulnerability

MODERATE
Advisory Summary

GHSA-c9vm-hv86-f23r is a MODERATE justhtml includes multiple security fixes vulnerability (CWE-755: Improper Handling of Exceptional Conditions) affecting Justhtml libraries in the PyPI ecosystem. The issue involves justhtml includes multiple security fixes. Remediation is available by upgrading affected packages to version 1.15.0.

GHSA-c9vm-hv86-f23r at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-c9vm-hv86-f23r
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-755: Improper Handling of Exceptional Conditions
Affected Product Justhtml
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-c9vm-hv86-f23r

To remediate this vulnerability, upgrade all affected Justhtml dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

justhtml fixed: 1.15.0
pip install justhtml>=1.15.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show justhtml

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-c9vm-hv86-f23r, inspect your installed packages using pip:

pip show justhtml

Analyze the terminal output to locate any version of Justhtml in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.0), your application is affected.

Note: The pip show justhtml command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-755: Improper Handling of Exceptional Conditions, where the product does not handle or incorrectly handles an exceptional condition. In Justhtml, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary `justhtml` `1.15.0` includes multiple security fixes affecting URL sanitization helpers, HTML serialization, Markdown passthrough, and several custom sanitization-policy edge cases. These issues have different impact levels and do not all affect the default configuration in the same way. ## Affected versions - `justhtml` `<= 1.14.0` ## Fixed version - `justhtml` `1.15.0` released on April 9, 2026 ## Impact overview ### Helper and serialization issues These issues could affect applications using JustHTML helpers or programmatic DOM construction, even outside the default HTML sanitization path. - `JustHTML.clean_url_value(...)` and `clean_url_in_js_string(...)` could accept URL values such as `javascript&#58...`, which became active `javascript:` URLs after HTML attribute parsing. - URL sanitization could treat values like `\\evil.example/x` or `/\\evil.example/x` as safe relative URLs even though browsers could resolve them as remote requests. - Malformed bracketed hosts such as `https://[evil.example]/x` could raise exceptions and crash sanitization when host allowlists were used. - Programmatic element or attribute names containing markup-breaking characters could be serialized into active HTML. - Programmatic HTML comments containing `-->` could break out of the comment and inject live markup. ### Markdown passthrough issue - `to_markdown(html_passthrough=True)` could reintroduce active HTML from sanitized `<textarea>` content by emitting a raw closing `</textarea>` sequence. ### Custom policy issues These issues affected custom policies more than the default safe configuration. - `a[ping]` was handled as a single URL even though browsers interpret it as a space-separated URL list. - `attributionsrc` was not treated as URL-bearing and could preserve attacker-controlled reporting endpoints. - `link[imagesrcset]` was not treated as URL-bearing and could preserve attacker-controlled image candidates. - Preserved `<meta http-equiv="refresh">` tags could keep redirect targets without URL-policy enforcement. - Preserved `<base href>` tags could rewrite how later relative URLs resolved in the browser. - Preserved `<style>` blocks could keep resource-loading CSS such as `@import`, `url(...)`, or `image-set(...)`. - Mixed-case attribute names in custom transform pipelines could bypass or confuse security-related transforms such as `DropAttrs(...)`, `DropUrlAttrs(...)`, `AllowStyleAttrs(...)`, and `MergeAttrs(...)`. ## Default configuration Most of the custom-policy issues above did **not** affect the default `JustHTML(..., sanitize=True)` behavior. The main exceptions were: - helper APIs such as `clean_url_value(...)` - programmatic DOM / serializer usage - applications explicitly using `html_passthrough=True` - applications using custom policies or custom transform pipelines ## Recommended action Upgrade to `justhtml` `1.15.0`. If you cannot upgrade immediately: - avoid `html_passthrough=True` for untrusted content - avoid preserving `<style>`, `<meta http-equiv="refresh">`, and `<base href>` in custom policies - avoid allowing `ping`, `attributionsrc`, or `imagesrcset` unless you explicitly validate them - avoid serializing untrusted programmatic node names, attribute names, or comment data

GHSA-c9vm-hv86-f23r Affected Justhtml Versions

1 component(s)
Fixed Versions:
1.15.0
Product / Package Ecosystem Affected Versions Fixed Version
justhtml
PyPI
< 1.15.0
1.15.0

References

Frequently Asked Questions

What is GHSA-c9vm-hv86-f23r?
GHSA-c9vm-hv86-f23r is a security vulnerability in Justhtml involving justhtml includes multiple security fixes under CWE-755: Improper Handling of Exceptional Conditions.
Which Justhtml versions are affected?
Affected versions include releases prior to 1.15.0 across affected packages: justhtml.
What version fixes GHSA-c9vm-hv86-f23r?
Upgrading to 1.15.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is justhtml affected?
Yes, justhtml is affected in releases prior to 1.15.0. Upgrade your dependency to 1.15.0 or later.
What CWE is associated with GHSA-c9vm-hv86-f23r?
GHSA-c9vm-hv86-f23r is classified under CWE-755: Improper Handling of Exceptional Conditions (The product does not handle or incorrectly handles an exceptional condition.).
How can I check PyPI dependencies for GHSA-c9vm-hv86-f23r?
Run the dependency tree command: 'pip show justhtml'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c9vm-hv86-f23r",
  "modified" : "2026-04-15T20:44:03Z",
  "published" : "2026-04-10T19:20:04Z",
  "aliases" : [ ],
  "summary" : "justhtml includes multiple security fixes",
  "details" : "## Summary\n\n`justhtml` `1.15.0` includes multiple security fixes affecting URL sanitization helpers, HTML serialization, Markdown passthrough, and several custom sanitization-policy edge cases.\n\nThese issues have different impact levels and do not all affect the default configuration in the same way.\n\n## Affected versions\n\n- `justhtml` `<= 1.14.0`\n\n## Fixed version\n\n- `justhtml` `1.15.0` released on April 9, 2026\n\n## Impact overview\n\n### Helper and serialization issues\nThese issues could affect applications using JustHTML helpers or programmatic DOM construction, even outside the default HTML sanitization path.\n\n- `JustHTML.clean_url_value(...)` and `clean_url_in_js_string(...)` could accept URL values such as `javascript&#58...`, which became active `javascript:` URLs after HTML attribute parsing.\n- URL sanitization could treat values like `\\\\evil.example/x` or `/\\\\evil.example/x` as safe relative URLs even though browsers could resolve them as remote requests.\n- Malformed bracketed hosts such as `https://[evil.example]/x` could raise exceptions and crash sanitization when host allowlists were used.\n- Programmatic element or attribute names containing markup-breaking characters could be serialized into active HTML.\n- Programmatic HTML comments containing `-->` could break out of the comment and inject live markup.\n\n### Markdown passthrough issue\n- `to_markdown(html_passthrough=True)` could reintroduce active HTML from sanitized `<textarea>` content by emitting a raw closing `</textarea>` sequence.\n\n### Custom policy issues\nThese issues affected custom policies more than the default safe configuration.\n\n- `a[ping]` was handled as a single URL even though browsers interpret it as a space-separated URL list.\n- `attributionsrc` was not treated as URL-bearing and could preserve attacker-controlled reporting endpoints.\n- `link[imagesrcset]` was not treated as URL-bearing and could preserve attacker-controlled image candidates.\n- Preserved `<meta http-equiv=\"refresh\">` tags could keep redirect targets without URL-policy enforcement.\n- Preserved `<base href>` tags could rewrite how later relative URLs resolved in the browser.\n- Preserved `<style>` blocks could keep resource-loading CSS such as `@import`, `url(...)`, or `image-set(...)`.\n- Mixed-case attribute names in custom transform pipelines could bypass or confuse security-related transforms such as `DropAttrs(...)`, `DropUrlAttrs(...)`, `AllowStyleAttrs(...)`, and `MergeAttrs(...)`.\n\n## Default configuration\n\nMost of the custom-policy issues above did **not** affect the default `JustHTML(..., sanitize=True)` behavior.\n\nThe main exceptions were:\n- helper APIs such as `clean_url_value(...)`\n- programmatic DOM / serializer usage\n- applications explicitly using `html_passthrough=True`\n- applications using custom policies or custom transform pipelines\n\n## Recommended action\n\nUpgrade to `justhtml` `1.15.0`.\n\nIf you cannot upgrade immediately:\n\n- avoid `html_passthrough=True` for untrusted content\n- avoid preserving `<style>`, `<meta http-equiv=\"refresh\">`, and `<base href>` in custom policies\n- avoid allowing `ping`, `attributionsrc`, or `imagesrcset` unless you explicitly validate them\n- avoid serializing untrusted programmatic node names, attribute names, or comment data",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "justhtml"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.15.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.14.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/EmilStenstrom/justhtml/security/advisories/GHSA-c9vm-hv86-f23r"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/EmilStenstrom/justhtml"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/EmilStenstrom/justhtml/compare/v1.14.0...v1.15.0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/EmilStenstrom/justhtml/releases/tag/v1.15.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-20", "CWE-755", "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-10T19:20:04Z",
    "nvd_published_at" : null
  }
}