CVE-2026-9496: Versions of the package pacote from 11.2.7 are vulnerable to Denial of Service (DoS) via the addGitSha func...
Versions of the package pacote from 11.2.7 are vulnerable to Denial of Service (DoS) via the addGitSha function. An attacker can exploit this vulnerability by supplying a specially crafted spec.rawSpec value that triggers the function’s regex replacement and string-manipulation logic, causing excessive CPU consumption and potentially stalling or crashing the process.
This flaw can let a remote attacker make software using vulnerable pacote consume excessive CPU and stall or crash. It is a denial-of-service issue, not described as data theft or code execution in the provided sources.
Executive priority
Treat this as a high-priority availability risk for systems that process untrusted package specifications. Prioritize inventory first, then update or isolate affected services when vendor guidance is available.
Technical view
CVE-2026-9496 affects pacote and org.webjars.npm:pacote at or from version 11.2.7. The addGitSha function can be driven by a crafted spec.rawSpec value into expensive regex replacement and string manipulation, causing high CPU consumption. The CVSS v4 score is 8.7 with high availability impact.
Likely exposure
Exposure is most likely in Node.js or Java applications that include pacote directly, via npm tooling, or through the WebJars npm package. Risk is higher where external users can influence package spec values processed by pacote.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but the provided sources do not describe active attacks.
Researcher notes
The evidence points to algorithmic complexity or uncontrolled resource consumption in addGitSha. The bundle does not provide a fixed version, patch commit, exploit details, or proof of active exploitation, so validation should stay dependency- and data-flow-focused.
Mitigation direction
Inventory direct and transitive use of pacote and org.webjars.npm:pacote.
Check npm, Snyk, and vendor guidance for fixed versions or official mitigations.
Update vulnerable dependencies once a safe version is identified by authoritative sources.
Avoid passing untrusted package spec values into affected processing paths where feasible.
Apply process resource limits and monitoring around services that process package specs.
Validation and detection
Review SBOMs, lockfiles, and dependency manifests for affected pacote packages.
Identify whether external input can influence spec.rawSpec values.
Confirm dependency updates remove the vulnerable version from runtime and build paths.
Monitor affected services for CPU spikes, stalls, or crashes during package-spec processing.
Based on public source material and reviewed before publication.
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.
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.
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.
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.
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.
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.