Skip to content

Auto-approve allows npm install execution of malicious postinstall acripts

High
mrubens published GHSA-c292-qxq4-4p2v Sep 4, 2025

Package

No package listed

Affected versions

< 3.26.0

Patched versions

3.26.0

Description

Summary

The extension contains a default list of allowed commands that do not need manual approval if auto-approve is enabled, and npm install was included in that list. Because npm install executes lifecycle scripts, if a repository’s package.json file contains a malicious postinstall script, it would be executed automatically without user approval. This means that enabling auto-approved commands and opening a malicious repo could result in arbitrary code execution.

Impact

This vulnerability allows an attacker to achieve arbitrary code execution on the developer’s system by placing a malicious postinstall (or similar lifecycle script) in package.json.

Remediation

The issue was fixed by removing dangerous commands from the default auto-approve allowlist as well as removing these previously default commands from the allowlist when the extension is updated.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE ID

CVE-2025-58374

Weaknesses

No CWEs

Credits