How severe is GHSA-ch52-vgq2-943f?

No CVSS score has been assigned to GHSA-ch52-vgq2-943f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ch52-vgq2-943f?

GHSA-ch52-vgq2-943f affects the following packages: marked (npm). Ecosystems affected: npm.

How do I fix GHSA-ch52-vgq2-943f?

Update marked to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ch52-vgq2-943f is resolved across your whole dependency graph.

How do I detect GHSA-ch52-vgq2-943f 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-ch52-vgq2-943f 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-ch52-vgq2-943f actively exploited in the wild?

No public exploit code has been indexed for GHSA-ch52-vgq2-943f 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.

When was GHSA-ch52-vgq2-943f published, and has it been updated?

GHSA-ch52-vgq2-943f was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Regular Expression Denial of Service in markedGHSA-ch52-vgq2-943f

GHSA-ch52-vgq2-943f is a security vulnerability in marked. A fix is available for marked — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, 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.

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

markednpm

121.1Mdownloads / week

Description

Affected versions of marked are vulnerable to Regular Expression Denial of Service (ReDoS). The _label subrule may significantly degrade parsing performance of malformed input.

Recommendation

Upgrade to version 0.7.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`marked`	≥ 0.4.0&&< 0.7.0	0.7.0`npm install marked@0.7.0`

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.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ch52-vgq2-943f 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

Affected versions of `marked` are vulnerable to Regular Expression Denial of Service (ReDoS). The `_label` subrule may significantly degrade parsing performance of malformed input. ## Recommendation Upgrade to version 0.7.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-ch52-vgq2-943f in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works