# CVE-2026-44705: tmp: Path Traversal via unsanitized prefix/postfix enables directory escape > Attackers can escape the temporary directory and create files in arbitrary locations by injecting path traversal sequences into tmp library options. - **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Jun 2026 - **Updated:** 13 Jun 2026 - **Also known as:** AZL-89765, CLEANSTART-2026-RI68041, CLSA-2026-1785117460, CLSA-2026-1785117462, CLSA-2026-1785204337, CLSA-2026-1785204339, CLSA-2026-1785204340, CLSA-2026-1785204341, CLSA-2026-1792777608, DEBIAN-CVE-2026-44705, ECHO-b579-7d1c-7a47, GHSA-ph9p-34f9-6g65, MINI-4rvj-3q4c-fgh7, MINI-6783-w73p-26xj, MINI-c2hg-9cx4-v3m4, MINI-c74h-fgrf-3ghv, MINI-f6jq-74xx-6w2v, MINI-f6q6-rhf3-97px, MINI-jrjh-84pp-p4ww, MINI-m4vx-fgw5-x393, MINI-mhrm-gx37-92x8, MINI-pqpg-46rc-ff56, MINI-pvxv-h7mv-rxx3, MINI-rhfg-77fr-847r, MINI-rq4w-8jw5-g2m5, MINI-w3xg-7wcq-vpxr, ROOT-APP-NPM-CVE-2026-44705, UBUNTU-CVE-2026-44705 ## What is CVE-2026-44705? CVE-2026-44705 is a high-severity path traversal vulnerability in raszi node-tmp, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description tmp is a temporary file and directory creator for node.js. Prior to 0.2.6, the tmp npm package contains a path traversal vulnerability that allows escaping the intended temporary directory when untrusted data flows into the prefix, postfix, or dir options. By embedding traversal sequences (e.g., ../) or path separators in these parameters, attackers can cause files to be created outside the configured temporary base directory at attacker-controlled locations with the privileges of the running process. This vulnerability affects applications that pass user-controlled data to tmp's file/directory creation functions without proper input sanitization. This vulnerability is fixed in 0.2.6. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-44705? 2 open source packages ship an affected version, including tmp. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tmp` | npm | All versions | 0.2.6 | | `tmp` | npm | All versions | 0.2.6 | Products: Raszi Tmp. ## How do I fix CVE-2026-44705? Upgrade tmp to 0.2.6 or later. ## Is CVE-2026-44705 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44705 exists. ## Other vulnerabilities in raszi node-tmp - [CVE-2026-49982](https://insights.sbomify.com/CVE-2026-49982/): tmp: Type-confusion bypass of _assertPath in tmp@0.2.6 allows path traversal via non-string prefix/postfix/template (high 8.2) - [CVE-2025-54798](https://insights.sbomify.com/CVE-2025-54798/): tmp does not restrict arbitrary temporary file / directory write via symbolic link `dir` parameter (low 2.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-44705 and fix it if it is affected. What it is: CVE-2026-44705 is a high-severity path traversal vulnerability in raszi node-tmp, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44705 exists. Affected packages and fixed versions: - tmp (npm): affected all versions; fixed in 0.2.6 - tmp (npm): affected all versions; fixed in 0.2.6 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-44705/ (Markdown: https://insights.sbomify.com/CVE-2026-44705/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44705 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44705 - OSV: https://osv.dev/vulnerability/CVE-2026-44705 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-44705/ Summaries are generated and may contain mistakes; the official description above is the record.