<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 23:10:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-5388 — justhtml before 1.15.0 Multiple Security Issues</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-5388</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; EmilStenstrom justhtml&lt;/p&gt;
&lt;p&gt;justhtml before 1.15.0 contains multiple security issues in URL sanitization helpers (clean_url_value/clean_url_in_js_string), HTML serialization, Markdown passthrough (html_passthrough=True), and several custom sanitization-policy edge cases. Depending on configuration, an attacker can bypass sanitization to inject active HTML and JavaScript — for example via encoded javascript: URLs, backslash-based relative URLs resolved as remote hosts, markup-breaking programmatic element/attribute names or HTML comments, raw &amp;lt;/textarea&amp;gt; reintroduction through Markdown passthrough, or preserved &amp;lt;style&amp;gt;/&amp;lt;meta http-equiv=refresh&amp;gt;/&amp;lt;base href&amp;gt; tags in custom policies. Most custom-policy issues do not affect the default sanitize=True configuration; they primarily affect helper APIs, programmatic DOM construction, html_passthrough=True, and custom policies/transform pipelines.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; EmilStenstrom justhtml&lt;/p&gt;
&lt;p&gt;justhtml before 1.15.0 contains multiple security issues in URL sanitization helpers (clean_url_value/clean_url_in_js_string), HTML serialization, Markdown passthrough (html_passthrough=True), and several custom sanitization-policy edge cases. Depending on configuration, an attacker can bypass sanitization to inject active HTML and JavaScript — for example via encoded javascript: URLs, backslash-based relative URLs resolved as remote hosts, markup-breaking programmatic element/attribute names or HTML comments, raw &amp;lt;/textarea&amp;gt; reintroduction through Markdown passthrough, or preserved &amp;lt;style&amp;gt;/&amp;lt;meta http-equiv=refresh&amp;gt;/&amp;lt;base href&amp;gt; tags in custom policies. Most custom-policy issues do not affect the default sanitize=True configuration; they primarily affect helper APIs, programmatic DOM construction, html_passthrough=True, and custom policies/transform pipelines.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-5388</guid>
    </item>
  </channel>
</rss>
