Security readout for executives and security teams
Plain-English summary
This is a local privilege escalation issue in npm CLI. A person who can already run low-privileged code on a machine may be able to make npm load code from an unsafe module location and run it as another target user. It matters most on shared developer systems, CI runners, and build servers.
Executive priority
Treat as high priority for shared development and build infrastructure because compromise can cross from low-privileged code to a target user. For isolated single-user systems, urgency is lower but inventory and vendor tracking are still needed.
Technical view
CVE-2026-0775 affects npm CLI 10.9.0 per the bundle. The flaw is incorrect permission assignment involving module handling: npm loads modules from an unsecured location, enabling local authenticated code execution in the target user's context. CVSS is 7.0 high with local attack vector, high complexity, low privileges, and high CIA impact.
Likely exposure
Exposure is most plausible where npm CLI 10.9.0 is installed on multi-user hosts, shared CI/build runners, or developer machines where low-privileged code can execute. The bundle does not establish broader version impact beyond 10.9.0, and default affected status is unknown.
Exploitation context
The sources describe a local attack requiring prior ability to run low-privileged code. There is no KEV listing in the bundle and no cited source here confirms active exploitation. The attack is high complexity but can result in arbitrary code execution as the target user.
Researcher notes
The bundle attributes the issue to unsecured module loading and CWE-732. Evidence is incomplete on fixed versions, exploit availability, and full affected-version range. Red Hat references and VEX data are listed, but this analysis should not assume remediation details absent from the provided sources.
Mitigation direction
- Inventory hosts and build images for npm CLI 10.9.0.
- Check npm, ZDI, and Red Hat guidance for fixed packages or vendor mitigations.
- Avoid running npm as privileged users on shared systems.
- Restrict untrusted local code execution on CI runners and developer hosts.
- Prioritize rebuilds of base images once vendor-fixed npm packages are available.
Validation and detection
- Confirm npm CLI versions on developer workstations, servers, and CI images.
- Identify systems where low-privileged users or jobs can run local code.
- Review build workflows that execute npm under privileged or shared target accounts.
- Track ZDI, CVE, and Red Hat records for patch or impact updates.
- Document whether each exposed environment is single-user, shared, or CI-controlled.
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-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0775 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
- High
- CVSS
- 7 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9zdiCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.0 score
7HighVector: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-23T04:02:55.468Z: Reported to Red Hat.
- 2026-01-23T03:29:14.622Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- ZDI-26-043CVE reference, zdi · x_research-advisory
- https://access.redhat.com/security/cve/CVE-2026-0775CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2432280CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-0775.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
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.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.