CYBER CODE RED

Get real-time updates on Telegram

P4

CVE-2026-50021: pnpm before 10.34.0 (exclusive), from 11.0.0 (inclusive), before 11.4.0 (exclusive), < 10.34.0, >= 11.0.0, < 11.4.0

CVE-2026-50021. CVSS 3.1 base score 8.1 (HIGH, NVD). EPSS 0.00181 (percentile 0.07605), scored 26-Oct-2026.

Affected technology

pnpm · before 10.34.0 (exclusive)
pnpm

pnpm · from 11.0.0 (inclusive), before 11.4.0 (exclusive)
pnpm

pnpm · < 10.34.0, >= 11.0.0, < 11.4.0
pnpm

Component: Not specified by the source

Attack conditions (Vendor/CNA, CVSS 3.1): Network (remote) · Low privileges required · No user interaction required

Attack conditions (NVD, CVSS 3.1): Network (remote) · Low privileges required · No user interaction required

What an attacker can do

If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL to serve altered package content, pnpm install --frozen-lockfile can install the altered package without an integrity error. npm's npm ci enforces integrity by default; pnpm's behavior of silently skipping verification is a pnpm-specific fail-open gap. Vendor/CNA’s CVSS 3.1 assessment (base score 6.8/10) rates confidentiality and integrity impact as high; availability impact as none. NVD’s CVSS 3.1 assessment (base score 8.1/10) rates confidentiality and integrity impact as high; availability impact as none.

Published

CWE
CWE-354
CCR priority
32.4 /100 (P4)
CVSS 3.1
8.1 /10 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N · NVD
EPSS
0.00181 · percentile 0.07743 · 2026-11-15
KEV
no

Provenance

Stable permalink: https://cybercodered.org/item/cve-cve-2026-50021.html