LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26311: GHSL-2020-312: Regular Expression Denial of Service (ReDoS) in useragent

Useragent is a user agent parser for Node.js. All versions as of time of publication contain one or more regular expressions that are vulnerable to Regular Expression Denial of Service (ReDoS). As of time of publication, no patches are available.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-26311 affects the Node.js useragent parser. A specially crafted user-agent string can make vulnerable regular expressions consume excessive CPU, causing denial of service. The source bundle says all versions were affected at publication and no patch was available then.

Executive priority

Treat as a high-priority availability risk for internet-facing Node.js services using this dependency. Prioritize inventory first, then remove, replace, or contain exposed parsing paths based on business criticality.

Technical view

The issue is CWE-1333 ReDoS in 3rd-Eden useragent. Network-reachable applications that parse attacker-controlled User-Agent headers may spend excessive time evaluating vulnerable regexes, impacting availability. CVSS v4.0 is 8.7 high with network access, low complexity, no privileges, and high availability impact.

Likely exposure

Exposure is most likely in Node.js services using the 3rd-Eden useragent package on public HTTP request paths, analytics ingestion, bot detection, logging enrichment, or middleware that parses untrusted User-Agent strings.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The practical risk is unauthenticated remote denial of service where user-agent parsing is reachable with attacker-controlled input.

Researcher notes

Evidence supports ReDoS in useragent and no patch at publication. The bundle’s affected-version metadata is sparse, so verify installed versions and vendor status directly before declaring remediation complete.

Mitigation direction

  • Inventory applications and lockfiles for the 3rd-Eden useragent package.
  • Check the GitHub advisory and issue for current vendor guidance.
  • Avoid parsing untrusted User-Agent strings with this package where feasible.
  • Consider replacement or isolation until vendor-supported remediation is available.
  • Apply operational controls for abuse: rate limits, CPU monitoring, and request filtering.

Validation and detection

  • Search dependency manifests and lockfiles for useragent package usage.
  • Trace request paths that pass User-Agent headers into the parser.
  • Confirm whether affected parsing is reachable without authentication.
  • Review production telemetry for CPU spikes tied to unusual User-Agent values.
  • Document compensating controls if removal or replacement is deferred.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1333: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-26311 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Green

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:GreenPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2020-26311Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Green

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
3rd-Edenuseragent0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.