How severe is GHSA-h6ch-v84p-w6p9?

No CVSS score has been assigned to GHSA-h6ch-v84p-w6p9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h6ch-v84p-w6p9?

GHSA-h6ch-v84p-w6p9 affects the following packages: diff (npm). Ecosystems affected: npm.

How do I fix GHSA-h6ch-v84p-w6p9?

Update diff to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6ch-v84p-w6p9 is resolved across your whole dependency graph.

How do I detect GHSA-h6ch-v84p-w6p9 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diff. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h6ch-v84p-w6p9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h6ch-v84p-w6p9?

O3 pinpoints whether GHSA-h6ch-v84p-w6p9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h6ch-v84p-w6p9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h6ch-v84p-w6p9 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-h6ch-v84p-w6p9 published, and has it been updated?

GHSA-h6ch-v84p-w6p9 was published on June 13, 2019 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-h6ch-v84p-w6p9

Fix: kpdecker/jsdiff@2aec429

GHSA-h6ch-v84p-w6p9 is a security vulnerability in diff. O3 Security confirms whether GHSA-h6ch-v84p-w6p9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Regular Expression Denial of Service (ReDoS)

Published

Jun 13, 2019

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

diffnpm

134.6Mdownloads / week

Description

A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`diff`	all versions	3.5.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diff. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update diff to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6ch-v84p-w6p9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h6ch-v84p-w6p9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h6ch-v84p-w6p9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.

O3 Security · Impact-Aware SCA

Is GHSA-h6ch-v84p-w6p9 in your dependencies?

O3 detects GHSA-h6ch-v84p-w6p9 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works