Secuno
ENNL
Book demo

CVE-2020-26308

Validatejs Validate.js vulnerability

7.5 HIGHPublic exploitEPSS 0.51%
  1. Published26 Oct 2024

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Validatejs Validate.js≤ 0.13.1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-826179.8
The two built-in name-finder patterns exposed by…
CVE-2026-527789.8
YesWiki is a wiki system written in PHP. Prior to version 4.6.6, an unsafe execution…
CVE-2026-354589.8
Gotenberg is an API for converting document formats. In 8.29.1 and earlier, Gotenberg…
CVE-2025-624848.1
Inefficient regular expression complexity in certain Zoom Workplace Clients before…

Frequently asked

Is CVE-2020-26308 being actively exploited?

CVE-2020-26308 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.51%.

How severe is CVE-2020-26308?

CVE-2020-26308 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.51% probability of exploitation.

Which products are affected by CVE-2020-26308?

Affected products include Validatejs Validate.js.

How do I fix CVE-2020-26308?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2020-26308 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.