CVE-2014-8882 — validator
HIGHCVE-2014-8882 is a high-severity (CVSS 7.5) vulnerability in validator. A fix is available for validator — see the affected versions and patch details below.
Regular Expression Denial of Service in validator
Real-World Exposure
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.
validatornpmDescription
Versions of validator prior to 3.22.1 are affected by a regular expression denial of service vulnerability in the isURL method.
Recommendation
Update to version 3.22.1 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | validator | all versions | 3.22.1npm install validator@3.22.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for validator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update validator to 3.22.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8882 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-8882 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2014-8882. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2014-8882 in your dependencies?
O3 Security finds CVE-2014-8882 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.