How severe is GHSA-rv73-9c8w-jp4c?

No CVSS score has been assigned to GHSA-rv73-9c8w-jp4c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rv73-9c8w-jp4c?

GHSA-rv73-9c8w-jp4c affects the following packages: validate.js (npm). Ecosystems affected: npm.

How do I fix GHSA-rv73-9c8w-jp4c?

The records we use list no patched version of validate.js for GHSA-rv73-9c8w-jp4c. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-rv73-9c8w-jp4c in my npm dependencies?

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

How do I mitigate GHSA-rv73-9c8w-jp4c 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-rv73-9c8w-jp4c actively exploited in the wild?

No public exploit code has been indexed for GHSA-rv73-9c8w-jp4c 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-rv73-9c8w-jp4c?

GHSA-rv73-9c8w-jp4c has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-rv73-9c8w-jp4c?

GHSA-rv73-9c8w-jp4c 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-rv73-9c8w-jp4c published, and has it been updated?

GHSA-rv73-9c8w-jp4c was published on October 26, 2024 and was last updated on October 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

validate.js Regular Expression Denial of Service vulnerability

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-rv73-9c8w-jp4c.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% 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.

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

validate.jsnpm

809Kdownloads / week

Description

Validate.js provides a declarative way of validating javascript objects. Versions 0.13.1 and prior contain one or more regular expressions that are vulnerable to Regular Expression Denial of Service (ReDoS). As of time of publication, no known patches are available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`validate.js`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

validate.jsvalidatejs

≤ 0.13.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for validate.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of validate.js for GHSA-rv73-9c8w-jp4c. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Validate.js provides a declarative way of validating javascript objects. Versions 0.13.1 and prior contain one or more regular expressions that are vulnerable to Regular Expression Denial of Service (ReDoS). As of time of publication, no known patches are available.

O3 Security · Impact-Aware SCA

Is GHSA-rv73-9c8w-jp4c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

validate.js Regular Expression Denial of Service vulnerabilityGHSA-rv73-9c8w-jp4c