<?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-30T21:32:52.608293+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-44708</id>
    <title>CVE-2026-44708 — Mistune Math Plugin XSS Escape Bypass</title>
    <updated>2026-09-30T21:32:52.612276+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> lepture mistune</p>
<p>Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.2.1, the mistune math plugin renders inline math ($...$) and block math ($$...$$) by concatenating the raw user-supplied content directly into the HTML output without any HTML escaping. This occurs even when the parser is explicitly created with escape=True, which is supposed to guarantee that all user-controlled text is sanitised before reaching the DOM. This vulnerability is fixed in 3.2.1.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-44708"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8g87-j6q8-g93x</id>
    <title>GHSA-8g87-j6q8-g93x — Mistune Math Plugin has an XSS Escape Bypass</title>
    <updated>2026-09-30T21:32:52.612527+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: mistune</p>
<p>## Summary
The mistune math plugin renders inline math (`$...$`) and block math (`$$...$$`) by concatenating the raw user-supplied content directly into the HTML output **without any HTML escaping**. This occurs even when the parser is explicitly created with `escape=True`, which is supposed to guarantee that all user-controlled text is sanitised before reaching the DOM.</p>
<p>The result is a silent contract violation: a developer who enables `escape=True` reasonably expects complete XSS protection, but the math plugin operates as an independent render path that ignores the renderer's `_escape` flag entirely.</p>
<p>## Details
**File:** `src/mistune/plugins/math.py`</p>
<p>```python
def render_inline_math(renderer, text):
    # `text` is raw user input — no escape() call anywhere
    return r'&lt;span class="math"&gt;\(' + text + r"\)&lt;/span&gt;"</p>
<p>def render_block_math(renderer, text):
    # same issue for block-level $$...$$
    return '&lt;div class="math"&gt;$$\n' + text + "\n$$&lt;/div&gt;\n"
```</p>
<p>Both functions take `text` directly from the parsed token and concatenate it into the output string. Neither function:
- calls `escape(text)` from `mistune.util`
- checks `renderer._escape`
- calls `safe_entity(text)` or any other sanitisation helper</p>
<p>The `escape=True` flag only influences the main `HTMLRenderer` methods (`paragraph`, `heading`, `codespan`, etc.). Plugin render functions registered via `md.renderer.register()` receive the `renderer` instance but have no mechanism that enforces the escape contract -…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8g87-j6q8-g93x"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-2206</id>
    <title>PYSEC-2026-2206</title>
    <updated>2026-09-30T21:32:52.612874+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: mistune</p>
<p>Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.2.1, the mistune math plugin renders inline math ($...$) and block math ($$...$$) by concatenating the raw user-supplied content directly into the HTML output without any HTML escaping. This occurs even when the parser is explicitly created with escape=True, which is supposed to guarantee that all user-controlled text is sanitised before reaching the DOM. This vulnerability is fixed in 3.2.1.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-2206"/>
  </entry>
</feed>
