{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101044 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-101044 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101044 is a high-severity path traversal vulnerability in pnpm, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-101044 and fix it if it is affected.\n\nWhat it is: CVE-2026-101044 is a high-severity path traversal vulnerability in pnpm, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-101044 in the wild and no public exploit code.\n\nAffected product: pnpm. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-101044/ (Markdown: https://insights.sbomify.com/CVE-2026-101044/index.md)","id":"CVE-2026-101044","markdown":"https://insights.sbomify.com/CVE-2026-101044/index.md","name":"CVE-2026-101044","record":{"aliases":["GHSA-qj85-gv7w-fqmr"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"pnpm package manager","requires_auth":"none","summary":"Attackers can create files outside project boundaries via malicious lockfile aliases, potentially leading to code execution or data modification.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"pacquet, the Rust package-manager component shipped in the pnpm npm package versions \u003e=12.0.0-alpha.0 and \u003c12.0.0-alpha.5, does not validate dependency alias/name paths taken from a lockfile before using them in install-time filesystem joins. When a user installs a project with an attacker-supplied lockfile using --trust-lockfile or a frozen lockfile, alias entries containing path traversal segments (for example '../../escaped-link') are used when creating dependency and package links, bin destinations, hoisted entries, and virtual-store slots, allowing symlinks and directories to be created outside the intended project and node_modules boundary. Version 12.0.0-alpha.5 validates dependency names and every virtual-store slot path with a shared safe-join containment helper before any filesystem materialization, rejecting traversal, absolute, platform-specific, and reserved names with ERR_PNPM_INVALID_DEPENDENCY_NAME.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"pacquet before 12.0.0-alpha.5 Path Traversal via lockfile alias","id":"CVE-2026-101044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Fleet Homebrew Cask OS Command Injection via Metadata","id":"CVE-2026-101045"},"packages":[],"prev":{"headline":"pnpm 11.0.0 before 11.11.0 Environment Variable Exfiltration via Proxy Settings","id":"CVE-2026-101043"},"products":["pnpm"],"published":"2026-09-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["pnpm"]},"summary":"Attackers can create files outside project boundaries via malicious lockfile aliases, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-101044/"}