cve.bz

CVE-2026-88753 Uncontrolled Resource Consumption

7.5 highEPSS 0.4%

High (7.5). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A Regular-Expression Denial of Service (ReDoS) in the Markdown2. extract_metadata() function (lib/markdown2.py) of trentm markdown2 through v2.5.5 allows attackers to cause a Denial of Service (DoS) via a crafted Markdown document.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-88753 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88753?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88753?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88753 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14python-markdown2no fix listedDEBIAN-CVE-2026-88753
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morepython-markdown2no fix listedUBUNTU-CVE-2026-88753
openSUSETumbleweedpython-markdown22.5.5-2.1openSUSE-SU-2026:12159-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-impact denial of service flaw was found in markdown2, which is shipped as a dependency in the OpenShift Container Platform 4 ose-olm-catalogd-rhel9 container image. When markdown2 renders a document with the opt-in `metadata` extra enabled, the extract_metadata() function applies an inefficient regular expression to attacker-controlled metadata values, and that pattern can take an exponential amount of time to process. A remote attacker who can supply a crafted Markdown document can trigger excessive CPU consumption in the rendering process, degrading or exhausting the availability of the service that renders it; confidentiality and integrity are not affected. Red Hat has rated this flaw MODERATE with a CVSS 3.1 base score of 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). Upstream analysis characterizes the issue as low-to-moderate because exploitation requires the opt-in `metadata` extra to be enabled, a meaningful difference from the Red Hat rating. For OpenShift Container Platform 4, the fix is deferred: this flaw is rated MODERATE severity with a CVSS score below 7.0, which does not meet the threshold for filing an update tracker at this time. The residual risk is limited to denial of service of the component that renders untrusted Markdown; there is no impact on confidentiality or integrity.

Red Hat's mitigation

The vulnerable code path is only reached when markdown2 is used with the opt-in `metadata` extra. Where feasible, applications that render untrusted Markdown should avoid enabling the `metadata` extra; upstream analysis confirms that the same input is processed in linear time when that extra is disabled. Bounding the length of accepted metadata values before parsing can also limit the resource consumption caused by crafted documents. Where these options are not applicable, mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4openshift4/ose-olm-catalogd-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88753.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON