cli: Incorrect Permission Assignment for Critical Resource
CVE-2026-0775 is a high-severity incorrect permission assignment for critical resource vulnerability in cli from Npm, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected cli versions: 10.9.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.29% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of cli you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Npm | cli | 10.9.0 | Not stated |
| Red Hat | Confidential Compute Attestation | Not specified in the record | Not stated |
| Red Hat | Cryostat 4 | Not specified in the record | Not stated |
| Red Hat | Logging Subsystem for Red Hat OpenShift | Not specified in the record | Not stated |
| Red Hat | Migration Toolkit for Containers | Not specified in the record | Not stated |
| Red Hat | Multicluster Engine for Kubernetes | Not specified in the record | Not stated |
| Red Hat | Network Observability Operator | Not specified in the record | Not stated |
| Red Hat | Node HealthCheck Operator | Not specified in the record | Not stated |
| Red Hat | OpenShift Lightspeed | Not specified in the record | Not stated |
| Red Hat | OpenShift Pipelines | Not specified in the record | Not stated |
| Red Hat | OpenShift Serverless | Not specified in the record | Not stated |
| Red Hat | Red Hat 3scale API Management Platform 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat AMQ Broker 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apache Camel - HawtIO 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat Connectivity Link 1 | Not specified in the record | Not stated |
| Red Hat | Red Hat Developer Hub | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux AI (RHEL AI) 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 10 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.0 | High | CNA |
| CVSS 3.0 | 7.0 | High | CNA (trendmicro.com) |
Official description
npm cli Incorrect Permission Assignment Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of npm cli. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of modules. The application loads modules from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of a target user. Was ZDI-CAN-25430.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 8.4 High severity
- 7.8 High severity
- 10.0 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.