How severe is CVE-2024-58382?

No CVSS score has been assigned to CVE-2024-58382 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-58382?

CVE-2024-58382 affects the following packages: league/commonmark (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-58382?

Update league/commonmark to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58382 is resolved across your whole dependency graph.

How do I detect CVE-2024-58382 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for league/commonmark, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-58382 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 CVE-2024-58382 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-58382 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 CVE-2024-58382?

CVE-2024-58382 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th 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 CVE-2024-58382?

CVE-2024-58382 is classified as CWE-407 (CWE-407). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-58382 published, and has it been updated?

CVE-2024-58382 was published on September 9, 2026 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2024-58382 — commonmark

CVE-2024-58382 is a CWE-407 vulnerability in league/commonmark. A fix is available for league/commonmark — see the affected versions and patch details below.

league/commonmark before 2.6.0 Denial of Service via Quadratic Complexity

Also known asGHSA-c2pc-g5qf-rfrf

Published

Sep 9, 2026

Updated

Oct 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-58382.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘league/commonmark

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Several polynomial time complexity issues in league/commonmark may lead to unbounded resource exhaustion and subsequent denial of service.

Malicious users could trigger that inefficient code with carefully crafted Markdown inputs that are specifically designed to ensure the worst-case performance is reached. Sending multiple such requests in parallel could tie up all available CPU resources and/or PHP-FPM processes, leading to denial of service for legitimate users.

Patches

These vulnerabilities have been patched in version 2.6.0. All users on older versions are highly encouraged to upgrade as soon as possible.

Workarounds

If you cannot upgrade, you may be able to mitigate the issues by:

Setting very low memory_limit and max_execution_time PHP configurations to prevent runaway resource usage
Implementing rate-limiting, bot protection, or other approaches to reduce the risk of simultaneous bad requests hitting your site
Limiting the size of inputs fed into this library (specifically the max length of each line)
Limiting the use of this library to trusted users

References

Most of these issues were discovered in other Markdown parsers. You can read more about them here:

For general information about this type of issue:

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`league/commonmark`	all versions	2.6.0`composer require league/commonmark:^2.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for league/commonmark, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update league/commonmark to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58382 is resolved across your whole dependency graph.
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 has rated this vulnerability as having an Important severity because unauthenticated remote attackers can cause complete service unavailability through CPU exhaustion without requiring privileges or user interaction. Applications utilizing this PHP library to process untrusted user input can have their worker…

Workaround published by Red Hat

Applications utilizing `league/commonmark` to process untrusted Markdown content should implement robust input validation and sanitization to prevent malicious inputs from reaching the parser. Additionally, consider deploying affected services within a sandboxed environment to limit resource consumption and potential impact from denial of service attacks.

Source: Red Hat security advisory for CVE-2024-58382 (CC BY 4.0)

Frequently Asked Questions

### Impact Several polynomial time complexity issues in league/commonmark may lead to unbounded resource exhaustion and subsequent denial of service. Malicious users could trigger that inefficient code with carefully crafted Markdown inputs that are specifically designed to ensure the worst-case performance is reached. Sending multiple such requests in parallel could tie up all available CPU resources and/or PHP-FPM processes, leading to denial of service for legitimate users. ### Patches These vulnerabilities have been patched in version 2.6.0. All users on older versions are highly enc

O3 Security · Impact-Aware SCA

Is CVE-2024-58382 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works