Security readout for executives and security teams
Plain-English summary
CVE-2026-0775 is a local privilege escalation issue in npm cli 10.9.0. A person who can already run low-privileged code on a system may be able to make npm load modules from an unsafe location and run code as another target user.
Executive priority
Treat as high priority for developer platforms, CI, and shared Unix-like hosts. It is not described as remotely exploitable, but it can turn an existing low-privileged foothold into higher-impact code execution in another user's context.
Technical view
The reported flaw is CWE-732, incorrect permission assignment, in npm cli module handling. Sources describe module loading from an unsecured location, enabling arbitrary code execution in the target user's context. CVSS 3.0 is 7.0 with local attack vector, high complexity, low privileges required, and no user interaction.
Likely exposure
Exposure is most relevant on systems with npm cli 10.9.0 where untrusted or low-privileged users can execute code, including shared hosts, CI runners, developer workstations, and build infrastructure. The bundle does not establish broader affected versions.
Exploitation context
The source bundle does not indicate known active exploitation, and KEV status is false. Exploitation requires prior local low-privileged code execution and is rated high complexity, limiting remote mass exploitation but raising concern on shared or compromised systems.
Researcher notes
Evidence identifies npm cli 10.9.0 and module loading from an unsecured location. The bundle does not provide exploit details, affected version ranges beyond 10.9.0, or a named fix. Validate against primary vendor and distribution advisories before concluding exposure.
Mitigation direction
- Check npm, Node.js, Red Hat, and ZDI guidance for fixed versions or vendor workarounds.
- Inventory and prioritize npm cli 10.9.0 on shared, CI, and privileged build systems.
- Limit local code execution access on affected hosts until vendor guidance is applied.
- Avoid running npm workflows under unnecessarily privileged user accounts.
- Monitor vendor advisories for patch availability and package rebuild status.
Validation and detection
- Confirm installed npm cli versions on developer, server, and CI assets.
- Identify systems where low-privileged users can run npm or arbitrary code.
- Review vendor records for whether your distribution marks packages affected or unaffected.
- Check endpoint and CI logs for unexpected npm execution by low-privileged users.
- Track whether remediation aligns with official vendor guidance, not assumptions.
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.