How severe is GHSA-p9wx-2529-fp83?

No CVSS score has been assigned to GHSA-p9wx-2529-fp83 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p9wx-2529-fp83?

GHSA-p9wx-2529-fp83 affects the following packages: marked (npm). Ecosystems affected: npm.

How do I fix GHSA-p9wx-2529-fp83?

Update marked to 0.3.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9wx-2529-fp83 is resolved across your whole dependency graph.

How do I detect GHSA-p9wx-2529-fp83 in my npm dependencies?

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

How do I mitigate GHSA-p9wx-2529-fp83 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-p9wx-2529-fp83 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9wx-2529-fp83 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-p9wx-2529-fp83?

GHSA-p9wx-2529-fp83 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th 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-p9wx-2529-fp83?

GHSA-p9wx-2529-fp83 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-p9wx-2529-fp83 published, and has it been updated?

GHSA-p9wx-2529-fp83 was published on May 23, 2025 and was last updated on May 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Marked allows Regular Expression Denial of Service…

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p9wx-2529-fp83.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

16Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

markednpm

125.7Mdownloads / week

Description

Marked prior to version 0.3.17 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to catastrophic backtracking in several regular expressions used for parsing HTML tags and markdown links. An attacker can exploit this vulnerability by providing specially crafted markdown input, such as deeply nested or repetitively structured brackets or tag attributes, which cause the parser to hang and lead to a Denial of Service.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`marked`	all versions	0.3.17`npm install marked@0.3.17`

Affected Products

1 product · 1 configurations

Application

markedmarked_project

< 0.3.17

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for marked, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update marked to 0.3.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9wx-2529-fp83 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.

Frequently Asked Questions

Marked prior to version 0.3.17 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to catastrophic backtracking in several regular expressions used for parsing HTML tags and markdown links. An attacker can exploit this vulnerability by providing specially crafted markdown input, such as deeply nested or repetitively structured brackets or tag attributes, which cause the parser to hang and lead to a Denial of Service.

O3 Security · Impact-Aware SCA

Is GHSA-p9wx-2529-fp83 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Marked allows Regular Expression Denial of Service (ReDoS) attacksGHSA-p9wx-2529-fp83