How severe is GHSA-3q64-rw38-243v?

No CVSS score has been assigned to GHSA-3q64-rw38-243v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3q64-rw38-243v?

Affected package information for GHSA-3q64-rw38-243v is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-3q64-rw38-243v?

Upgrade the affected component to the fixed release for GHSA-3q64-rw38-243v, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-3q64-rw38-243v in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-3q64-rw38-243v if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-3q64-rw38-243v actively exploited in the wild?

No public exploit code has been indexed for GHSA-3q64-rw38-243v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3q64-rw38-243v?

GHSA-3q64-rw38-243v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3q64-rw38-243v?

GHSA-3q64-rw38-243v is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3q64-rw38-243v published, and has it been updated?

GHSA-3q64-rw38-243v was published on October 22, 2026 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Mistune 3.0.0 before 3.3.0 Denial of Service via Nested…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Mistune from 3.0.0 before 3.3.0 contains an algorithmic complexity denial of service vulnerability in the parse_link_text function in src/mistune/helpers.py. Attackers can submit markdown with deeply nested square brackets triggering quadratic parsing time, exhausting server CPU with small crafted requests.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-3q64-rw38-243v, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Product Security rates this vulnerability as having an Important severity because remote attackers can induce significant CPU resource exhaustion and service unavailability with minimal request overhead. Within Red Hat OpenShift AI container images and runtime workbenches, mistune processes user-supplied text…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for GHSA-3q64-rw38-243v (CC BY 4.0)

Frequently Asked Questions

Mistune from 3.0.0 before 3.3.0 contains an algorithmic complexity denial of service vulnerability in the parse_link_text function in src/mistune/helpers.py. Attackers can submit markdown with deeply nested square brackets triggering quadratic parsing time, exhausting server CPU with small crafted requests.

O3 Security · Impact-Aware SCA

Is GHSA-3q64-rw38-243v in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

Mistune 3.0.0 before 3.3.0 Denial of Service via Nested Bracket ParsingGHSA-3q64-rw38-243v