<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T23:46:17.474815+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-8445</id>
    <title>CVE-2026-8445 — justhtml before 1.12.0 Sanitizer Bypass via Markdown</title>
    <updated>2026-09-29T23:46:17.966582+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> EmilStenstrom justhtml</p>
<p>justhtml versions &lt;= 1.11.0 (fixed in 1.12.0) do not sufficiently escape HTML-significant characters (angle brackets) in text nodes when converting a parsed document to Markdown via to_markdown(). While a small set of Markdown metacharacters are escaped, characters such as &lt; and &gt; are preserved, so untrusted input that is safe in to_html() — including entity-decoded text (e.g. &amp;lt;script&amp;gt;) or text from RCDATA/RAWTEXT-parsed elements like &lt;title&gt;, &lt;textarea&gt;, &lt;noscript&gt;, and &lt;plaintext&gt; — can be emitted as raw HTML in the Markdown output, enabling a sanitizer bypass and potential cross-site scripting when that output is rendered.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-8445"/>
  </entry>
</feed>
