Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY31 SECURITY RECORDS

pnpm

pnpm

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at pnpm, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-101044 27 Sep 2026 pnpm: 12.0.0-alpha.0 < 12.0.0-alpha.5 pnpm: 12.0.0-alpha.5 Update reference ↗
CVE-2026-101043 27 Sep 2026 pnpm: 11.0.0 < 11.11.0, 10.7.0 < 10.34.5 pnpm: 11.11.0, 10.34.5 Update reference ↗
CVE-2026-82393 31 Aug 2026 < 10.34.5; >= 11.0.0, < 11.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82392 31 Aug 2026 < 10.34.5; >= 11.0.0, < 11.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-59195 6 Jul 2026 < 10.34.4; >= 11.0.0, < 11.8.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-59196 6 Jul 2026 < 10.34.4; >= 11.0.0, < 11.7.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-59194 6 Jul 2026 < 10.34.4; >= 11.0.0, < 11.7.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-55180 25 Jun 2026 < 10.34.2; >= 11.0.0, < 11.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48995 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-50017 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-50016 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-50015 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-50014 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-50573 25 Jun 2026 < 10.33.4; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-50021 25 Jun 2026 < 10.34.0; >= 11.0.0, < 11.4.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-55700 25 Jun 2026 >= 11.3.0, < 11.5.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-55699 25 Jun 2026 < 10.34.2; >= 11.0.0, < 11.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-55698 25 Jun 2026 < 10.34.2; >= 11.0.0, < 11.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-55697 25 Jun 2026 < 10.34.2; >= 11.0.0, < 11.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-55487 25 Jun 2026 < 10.34.2; >= 11.0.0, < 11.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24131 26 Jan 2026 < 10.28.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-24056 26 Jan 2026 < 10.28.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-23890 26 Jan 2026 < 10.28.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-23889 26 Jan 2026 < 10.28.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-23888 26 Jan 2026 < 10.28.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2025-69262 7 Jan 2026 >=6.25.0, < 10.27.0 10.27.0. Update reference ↗
CVE-2025-69264 7 Jan 2026 pnpm: > 10.0.0, < 10.26.0 10.26.0. Update reference ↗
CVE-2025-69263 7 Jan 2026 pnpm: < 10.26.0 10.26.0. Update reference ↗
CVE-2024-47829 23 Apr 2025 < 10.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53866 10 Dec 2024 < 9.15.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-37478 1 Aug 2023 < 7.33.4; >= 8.0.0, < 8.6.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.