Bug 2512406 - CVE-2026-67422 python-pymdown-extensions: Pymdown-extensions: Denial of Service via Regular Expression Vulnerability [epel-all]
Summary: CVE-2026-67422 python-pymdown-extensions: Pymdown-extensions: Denial of Servi...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-pymdown-extensions
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["947a1a9a-58dc-4af1-825c-f...
Depends On:
Blocks: CVE-2026-67422
TreeView+ depends on / blocked
 
Reported: 2026-08-07 05:31 UTC by Marian Rehak
Modified: 2026-08-07 05:31 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2026-08-07 05:31:31 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

pymdown-extensions is a collection of extensions for the Python Markdown library. In versions up to and including 11.0, four inline processors (caret, tilde, betterem, and magiclink) use regular expressions whose content groups can partition a run of delimiter characters in exponentially many ways, causing catastrophic backtracking. As a result, a single untrusted Markdown line under 50 bytes rendered with markdown.markdown() in each extension's default configuration drives the rendering thread into unbounded CPU usage that grows exponentially with input length, enabling an unauthenticated remote attacker who can submit Markdown to cause denial of service. The exposure is concrete for web applications that render user-supplied Markdown (comments, wikis, issue bodies, live preview), including any app using pymdownx.extra which bundles the vulnerable betterem default, as well as hosted docs/CI systems that build untrusted Markdown. The issue has been fixed in version 11.0.1.


Note You need to log in before you can comment on or make changes to this bug.