{"answers":{"affected":"4 open source packages ship an affected version, including pnpm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50021 in the wild and no public exploit code.","fix":"Upgrade pnpm to a fixed version for your release line: 10.34.1 or 11.4.0.","what":"CVE-2026-50021 is a medium-severity vulnerability in pnpm, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50021 and fix it if it is affected.\n\nWhat it is: CVE-2026-50021 is a medium-severity vulnerability in pnpm, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50021 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pnpm (npm): affected all versions; fixed in 10.34.1\n- pnpm (npm): affected all versions; fixed in 10.34.1\n- pnpm (npm): affected from 11.0.0; fixed in 11.4.0\n- pnpm (npm): affected from 11.0.0; fixed in 11.4.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50021/ (Markdown: https://insights.sbomify.com/CVE-2026-50021/index.md)","id":"CVE-2026-50021","markdown":"https://insights.sbomify.com/CVE-2026-50021/index.md","name":"CVE-2026-50021","record":{"aliases":["GHSA-q6j5-fjx5-2mc3","MINI-5fwg-5f27-jj39","ROOT-APP-NPM-CVE-2026-50021"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"pnpm package manager","requires_auth":"low_privilege","summary":"Attackers can bypass integrity checks in pnpm by removing lockfile fields, allowing installation of malicious packages during frozen installs.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pnpm","vendor":"pnpm"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field","id":"CVE-2026-50021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Metacat acts as unintended proxy to backend Apache SOLR engine","id":"CVE-2026-50022"},"packages":[{"ecosystem":"npm","fixed":["10.34.1"],"introduced":["0"],"last_affected":[],"package":"pnpm","purl":null,"source":"GHSA-q6j5-fjx5-2mc3"},{"ecosystem":"npm","fixed":["10.34.1"],"introduced":["0"],"last_affected":[],"package":"pnpm","purl":"pkg:npm/pnpm","source":"GHSA-q6j5-fjx5-2mc3"},{"ecosystem":"npm","fixed":["11.4.0"],"introduced":["11.0.0"],"last_affected":[],"package":"pnpm","purl":null,"source":"GHSA-q6j5-fjx5-2mc3"},{"ecosystem":"npm","fixed":["11.4.0"],"introduced":["11.0.0"],"last_affected":[],"package":"pnpm","purl":"pkg:npm/pnpm","source":"GHSA-q6j5-fjx5-2mc3"}],"prev":{"headline":"Netty's HttpObjectDecoder skips arbitrary initial control characters when only initial CRLF characters are permitted","id":"CVE-2026-50020"},"products":["pnpm"],"published":"2026-06-25","related":[{"cvss_score":8.8,"headline":"pnpm: Transitive dependency alias path traversal allows project path override via symlink replacement","id":"CVE-2026-50016","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.8,"headline":"pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes","id":"CVE-2026-55698","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.8,"headline":"pnpm v10+ Bypass \"Dependency lifecycle scripts execution disabled by default\"","id":"CVE-2025-69264","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":8.8,"headline":"Untrusted Search Path in PNPM","id":"CVE-2022-26183","kev_date_added":null,"published":"2022-03-21"},{"cvss_score":8.2,"headline":"pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config","id":"CVE-2026-59195","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":7.6,"headline":"pnpm vulnerable to Command Injection via environment variable substitution","id":"CVE-2025-69262","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":7.5,"headline":"pnpm: manifest identity spoof satisfies allowBuilds and runs attacker lifecycle","id":"CVE-2026-55487","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["pnpm"]},"summary":"Attackers can bypass integrity checks in pnpm by removing lockfile fields, allowing installation of malicious packages during frozen installs.","url":"https://insights.sbomify.com/CVE-2026-50021/"}