pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| pnpm | pnpm | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Pnpm | Pnpm |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-q6j5-fjx5-2mc3 | pnpm Has an Integrity Check Bypass via Missing Lockfile Integrity Field |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.181% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-494 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pnpm
Pnpm pnpm |
|
| Vendors & Products |
Pnpm
Pnpm pnpm |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. 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. This vulnerability is fixed in 10.34.0 and 11.4.0. | |
| Title | pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field | |
| Weaknesses | CWE-354 | |
| References |
| |
| Metrics |
cvssV3_1
|