<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 10:27:56 +0000</lastBuildDate>
    <item>
      <title>BREW-adr-viewer-CVE-2026-59930 — Mistune toc / TableOfContents directive: heading IDs use predictable `toc_N` numbering with no slugification, allowing…</title>
      <link>https://cve.radiocsirt.org/vuln/brew-adr-viewer-cve-2026-59930</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: adr-viewer&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Predictable identifier generation. The `toc` plugin and `TableOfContents` directive both default to generating heading IDs of the form `toc_1`, `toc_2`, `toc_3`, ... with no input-derived component. An attacker who can place a heading anywhere in the document can predict which `toc_N` ID it will receive, and can inject HTML elsewhere (in a non-heading context) that uses the same `id=&amp;#34;toc_N&amp;#34;` to either (a) shadow the legitimate heading anchor, breaking same-page navigation, or (b) collide with CSS or JavaScript that targets `#toc_N` selectors, redirecting click handlers and styling to attacker-chosen content.
**File:** `src/mistune/toc.py` line 36-37 (`heading_id = lambda token, index: &amp;#34;toc_&amp;#34; + str(index + 1)`); `src/mistune/directives/toc.py` line 33 (same default).
**Root cause:** the default `heading_id` callback ignores the heading&amp;#39;s text content and uses only the headings&amp;#39;s order in the document. Two documents rendered together (or one document with attacker-influenced headings spliced into trusted content) produce overlapping `toc_N` IDs. Because `id` attribute uniqueness is required by HTML, browsers behaviour on duplicate IDs is undefined; `document.getElementById(&amp;#39;toc_1&amp;#39;)` returns the first match, `getElementsByTagName + querySelector` semantics differ across paths, and CSS rules targeting `#toc_1` apply to whichever element matches first in tree order.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File:** `src/mistune/toc.py`, lines 33-39.&lt;/p&gt;
&lt;p&gt;```python
def add_toc_hook(m…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: adr-viewer&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Predictable identifier generation. The `toc` plugin and `TableOfContents` directive both default to generating heading IDs of the form `toc_1`, `toc_2`, `toc_3`, ... with no input-derived component. An attacker who can place a heading anywhere in the document can predict which `toc_N` ID it will receive, and can inject HTML elsewhere (in a non-heading context) that uses the same `id=&amp;#34;toc_N&amp;#34;` to either (a) shadow the legitimate heading anchor, breaking same-page navigation, or (b) collide with CSS or JavaScript that targets `#toc_N` selectors, redirecting click handlers and styling to attacker-chosen content.
**File:** `src/mistune/toc.py` line 36-37 (`heading_id = lambda token, index: &amp;#34;toc_&amp;#34; + str(index + 1)`); `src/mistune/directives/toc.py` line 33 (same default).
**Root cause:** the default `heading_id` callback ignores the heading&amp;#39;s text content and uses only the headings&amp;#39;s order in the document. Two documents rendered together (or one document with attacker-influenced headings spliced into trusted content) produce overlapping `toc_N` IDs. Because `id` attribute uniqueness is required by HTML, browsers behaviour on duplicate IDs is undefined; `document.getElementById(&amp;#39;toc_1&amp;#39;)` returns the first match, `getElementsByTagName + querySelector` semantics differ across paths, and CSS rules targeting `#toc_1` apply to whichever element matches first in tree order.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File:** `src/mistune/toc.py`, lines 33-39.&lt;/p&gt;
&lt;p&gt;```python
def add_toc_hook(m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-adr-viewer-cve-2026-59930</guid>
    </item>
    <item>
      <title>EUVD-2026-335303</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335303</link>
      <description>EUVD-2026-335303</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335303</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59930</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59930</link>
      <description>&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59930</guid>
    </item>
    <item>
      <title>GHSA-2hm2-hc3v-44h9 — Mistune toc / TableOfContents directive: heading IDs use predictable `toc_N` numbering with no slugification, allowing…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2hm2-hc3v-44h9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mistune&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Predictable identifier generation. The `toc` plugin and `TableOfContents` directive both default to generating heading IDs of the form `toc_1`, `toc_2`, `toc_3`, ... with no input-derived component. An attacker who can place a heading anywhere in the document can predict which `toc_N` ID it will receive, and can inject HTML elsewhere (in a non-heading context) that uses the same `id=&amp;#34;toc_N&amp;#34;` to either (a) shadow the legitimate heading anchor, breaking same-page navigation, or (b) collide with CSS or JavaScript that targets `#toc_N` selectors, redirecting click handlers and styling to attacker-chosen content.
**File:** `src/mistune/toc.py` line 36-37 (`heading_id = lambda token, index: &amp;#34;toc_&amp;#34; + str(index + 1)`); `src/mistune/directives/toc.py` line 33 (same default).
**Root cause:** the default `heading_id` callback ignores the heading&amp;#39;s text content and uses only the headings&amp;#39;s order in the document. Two documents rendered together (or one document with attacker-influenced headings spliced into trusted content) produce overlapping `toc_N` IDs. Because `id` attribute uniqueness is required by HTML, browsers behaviour on duplicate IDs is undefined; `document.getElementById(&amp;#39;toc_1&amp;#39;)` returns the first match, `getElementsByTagName + querySelector` semantics differ across paths, and CSS rules targeting `#toc_1` apply to whichever element matches first in tree order.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File:** `src/mistune/toc.py`, lines 33-39.&lt;/p&gt;
&lt;p&gt;```python
def add_toc_hook(m…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mistune&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Predictable identifier generation. The `toc` plugin and `TableOfContents` directive both default to generating heading IDs of the form `toc_1`, `toc_2`, `toc_3`, ... with no input-derived component. An attacker who can place a heading anywhere in the document can predict which `toc_N` ID it will receive, and can inject HTML elsewhere (in a non-heading context) that uses the same `id=&amp;#34;toc_N&amp;#34;` to either (a) shadow the legitimate heading anchor, breaking same-page navigation, or (b) collide with CSS or JavaScript that targets `#toc_N` selectors, redirecting click handlers and styling to attacker-chosen content.
**File:** `src/mistune/toc.py` line 36-37 (`heading_id = lambda token, index: &amp;#34;toc_&amp;#34; + str(index + 1)`); `src/mistune/directives/toc.py` line 33 (same default).
**Root cause:** the default `heading_id` callback ignores the heading&amp;#39;s text content and uses only the headings&amp;#39;s order in the document. Two documents rendered together (or one document with attacker-influenced headings spliced into trusted content) produce overlapping `toc_N` IDs. Because `id` attribute uniqueness is required by HTML, browsers behaviour on duplicate IDs is undefined; `document.getElementById(&amp;#39;toc_1&amp;#39;)` returns the first match, `getElementsByTagName + querySelector` semantics differ across paths, and CSS rules targeting `#toc_1` apply to whichever element matches first in tree order.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File:** `src/mistune/toc.py`, lines 33-39.&lt;/p&gt;
&lt;p&gt;```python
def add_toc_hook(m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2hm2-hc3v-44h9</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-59930 — Mistune toc / TableOfContents directive: heading IDs use predictable `toc_N` numbering with no slugification, allowing…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-59930</link>
      <description>msrc_CVE-2026-59930</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-59930</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21339-1 — Security update for python-mistune</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21339-1</link>
      <description>&lt;p&gt;Security update for python-mistune&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-mistune&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21339-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-2218</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2218</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mistune&lt;/p&gt;
&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mistune&lt;/p&gt;
&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2218</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22655-1 — Security update for python-mistune</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22655-1</link>
      <description>&lt;p&gt;Security update for python-mistune&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-mistune&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22655-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-59930</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59930</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: mistune, Ubuntu:18.04:LTS: mistune, Ubuntu:20.04:LTS: mistune, Ubuntu:22.04:LTS: mistune, Ubuntu:24.04:LTS: mistune, Ubuntu:25.10: mistune, Ubuntu:26.04:LTS: mistune&lt;/p&gt;
&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: mistune, Ubuntu:18.04:LTS: mistune, Ubuntu:20.04:LTS: mistune, Ubuntu:22.04:LTS: mistune, Ubuntu:24.04:LTS: mistune, Ubuntu:25.10: mistune, Ubuntu:26.04:LTS: mistune&lt;/p&gt;
&lt;p&gt;Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id=&amp;#34;toc_N&amp;#34; content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59930</guid>
    </item>
  </channel>
</rss>
