How many CVEs have patched _find_end_marker?

1 published CVEs changed _find_end_marker in lepture/mistune, in 1 distinct patches totalling 34 changed lines, between 2026 and 2026.

What is the latest CVE that changed _find_end_marker?

CVE-2026-59922 (Mistune plugins/formatting: quadratic-time parsing on long runs of `~~x~~`, `==x==`, and `^^x^^` markers (strikethrough / mark / insert)), published 2026-07-08, changed lines 75 to 108 of src/mistune/plugins/formatting.py.

How does _find_end_marker compare to the rest of lepture/mistune?

lepture/mistune has 14 CVEs with a located fix in total; 1 of them changed _find_end_marker.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

lepture/mistune

Function

_find_end_marker

Name: _find_end_marker in lepture/mistune: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/mistune/plugins/formatting.py

Last patched July 8, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

34

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_find_end_marker in lepture/mistune was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 34 lines in total.

lepture/mistune has 14 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _find_end_marker, newest first, with the lines each fix touched.

Mistune plugins/formatting: quadratic-time parsing on long runs of `~~x~~`, `==x==`, and `^^x^^` markers (strikethrough / mark / insert)
CVE-2026-59922 · lines 75–108 · +34 −0
High · CVSS 7.5
EPSS 0.6%2026-07-08

Get an alert when the next CVE fix lands in lepture/mistune, with the patched functions.

Monitor mistune CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in lepture/mistune changed by the most CVE fixes.

__init__2 CVEs · src/mistune/inline_parser.py render_html_include2 CVEs · src/mistune/directives/include.py parse2 CVEs · src/mistune/directives/include.py _unquote_url2 CVEs · src/mistune/renderers/html.py safe_url2 CVEs · src/mistune/renderers/html.py render_figure2 CVEs · src/mistune/directives/image.py

All patched functions in lepture/mistune

Frequently asked questions

Common questions about CVE fixes to _find_end_marker.

How many CVEs have patched _find_end_marker?: 1 published CVEs changed _find_end_marker in lepture/mistune, in 1 distinct patches totalling 34 changed lines, between 2026 and 2026.
What is the latest CVE that changed _find_end_marker?: CVE-2026-59922 (Mistune plugins/formatting: quadratic-time parsing on long runs of `~~x~~`, `==x==`, and `^^x^^` markers (strikethrough / mark / insert)), published 2026-07-08, changed lines 75 to 108 of src/mistune/plugins/formatting.py.
How does _find_end_marker compare to the rest of lepture/mistune?: lepture/mistune has 14 CVEs with a located fix in total; 1 of them changed _find_end_marker.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track lepture/mistune CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing