critical

CVE-2025-69264

pnpm: pnpm code execution

Published 7 Jan 2026Modified 14 Oct 2026CWE 693

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

GHSA8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Red Hat8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by GHSA (high), Red Hat (high).

Description

pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature "Dependency lifecycle scripts execution disabled by default". While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0.

Affected packages and fixed versions

Source	Package	Fixed in
alpine 3.23	pnpm	10.33.4-r0
minimos	pnpm	10.26.0-r0
npm::GitHub Security Advisory npm	pnpm	10.26.0
rapidfort alpine 3.20	pnpm	10.26.0-r0
rapidfort alpine 3.21	pnpm	10.26.0-r0
rapidfort alpine 3.22	pnpm	10.26.0-r0
rapidfort fedora 43	nodejs-pnpm, pnpm	10.27.0-1.fc43

Show all 8 entries from 7 sources

Source	Package	Fixed in
alpine 3.23	pnpm	10.33.4-r0
minimos	pnpm	10.26.0-r0
npm::GitHub Security Advisory npm	pnpm	10.26.0
rapidfort alpine 3.20	pnpm	10.26.0-r0
rapidfort alpine 3.21	pnpm	10.26.0-r0
rapidfort alpine 3.22	pnpm	10.26.0-r0
rapidfort fedora 43	nodejs-pnpm	10.27.0-1.fc43
rapidfort fedora 43	pnpm	10.27.0-1.fc43

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs