Security readout for executives and security teams
Plain-English summary
Minimatch versions 3.0.1 and earlier can spend excessive processing time on crafted glob patterns. If an application lets users supply patterns processed by minimatch, this can become a denial-of-service risk. The source bundle provides no CVSS score and no evidence of active exploitation.
Executive priority
Treat as a targeted availability risk, not a confirmed breach signal. Prioritize systems where public or customer input can trigger minimatch pattern processing.
Technical view
The vulnerability is a regular expression denial of service issue in the pattern parameter of minimatch(path, pattern). Minimatch converts glob expressions into JavaScript RegExp objects, and affected versions can trigger uncontrolled resource consumption. Affected package scope is minimatch node module <=3.0.1.
Likely exposure
Exposure is most likely in Node.js applications or tooling that include minimatch <=3.0.1 and process untrusted or user-controlled glob patterns.
Exploitation context
CISA KEV status is false in the bundle, and no cited source states active exploitation. Practical impact depends on whether attackers can influence the pattern parameter in a reachable workflow.
Researcher notes
The source evidence is narrow: affected versions, ReDoS class, and vulnerable parameter are identified, but scoring, exploit prevalence, and exact fixed version are not included in the bundle.
Mitigation direction
- Inventory Node.js dependencies for minimatch <=3.0.1.
- Update minimatch according to package or vendor advisory guidance.
- Avoid accepting untrusted glob patterns where possible.
- Apply input limits and request timeouts around pattern-processing workflows.
Validation and detection
- Check lockfiles and dependency trees for minimatch versions.
- Confirm whether user-controlled input reaches minimatch pattern handling.
- Review public routes, APIs, or jobs that process glob patterns.
- Retest affected workflows after dependency updates or input restrictions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-400: 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 lookupCVE-2016-10540 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/118CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.