CyberSecBulletin
CVE-2026-0775NVD status: Deferred

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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of cli you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Npmcli10.9.0Not stated
Red HatConfidential Compute AttestationNot specified in the recordNot stated
Red HatCryostat 4Not specified in the recordNot stated
Red HatLogging Subsystem for Red Hat OpenShiftNot specified in the recordNot stated
Red HatMigration Toolkit for ContainersNot specified in the recordNot stated
Red HatMulticluster Engine for KubernetesNot specified in the recordNot stated
Red HatNetwork Observability OperatorNot specified in the recordNot stated
Red HatNode HealthCheck OperatorNot specified in the recordNot stated
Red HatOpenShift LightspeedNot specified in the recordNot stated
Red HatOpenShift PipelinesNot specified in the recordNot stated
Red HatOpenShift ServerlessNot specified in the recordNot stated
Red HatRed Hat 3scale API Management Platform 2Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2Not specified in the recordNot stated
Red HatRed Hat AMQ Broker 7Not specified in the recordNot stated
Red HatRed Hat Ansible Automation Platform 2Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel - HawtIO 4Not specified in the recordNot stated
Red HatRed Hat Connectivity Link 1Not specified in the recordNot stated
Red HatRed Hat Developer HubNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux AI (RHEL AI) 3Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8Not specified in the recordNot 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 systemScoreSeverityScored by
CVSS 3.17.0HighCNA
CVSS 3.07.0HighCNA (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

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Incorrect Permission Assignment for Critical Resource vulnerabilities

Spotted an error? Tell us.