CISA list

pnpm versions

pnpm: update to 12.22.0, 11.28.13 or 10.34.9. 9 and older no longer get fixes.

Data: .

Which pnpm branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.

Which pnpm branch to run
BranchStatusNewest safe releaseUpgrade to
12Fixes, no end date announced12.22.012.22.0 (this branch)
1119 CVE records that this page readsFixes until 30 April 202711.28.1311.28.13 (this branch)
1027 CVE records that this page readsFixes until 30 April 202710.34.910.34.9 (this branch)
91 CVE record that this page readsEnded on 30 April 2026None, the branch has ended10.34.9 (move to 10)
81 CVE record that this page readsEnded on 30 April 2025None, the branch has ended10.34.9 (move to 10)
71 CVE record that this page readsEnded on 16 April 2024None, the branch has ended10.34.9 (move to 10)
6Ended on 20 March 2023None, the branch has ended10.34.9 (move to 10)
5Ended on 29 April 2022None, the branch has ended10.34.9 (move to 10)
4Ended on 24 April 2021None, the branch has ended10.34.9 (move to 10)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 31 CVE records that the CVE Numbering Authorities GitHub_M and VulnCheck (as the CVE List names them) published and that name pnpm. The fixes are from the 30 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.

1 record is not placed on a branch, so no branch or release row counts it: CVE-2026-101044.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)