Quick answers
- Is CVE-2026-44705 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44705 being exploited in the wild.
- How severe is CVE-2026-44705?
- High severity, with a CVSS score of 4, published 11 June 2026.
- Which products and versions are affected?
- tmp (npm) < 0.2.6, SEMVER:introduced=0,fixed=0.2.6.
- Is there a fix for CVE-2026-44705?
- Yes. tmp (npm): upgrade to 0.2.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44705 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44705?
- Check whether you run tmp (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- tmp (npm): upgrade to 0.2.6 or later
npm install tmp@0.2.6
Technical details
A path traversal vulnerability exists in the 'tmp' npm package due to insufficient sanitization of the 'prefix', 'postfix', and 'dir' options. The library uses 'path.join()' to construct file paths by concatenating these user-supplied strings with the temporary directory path. Because 'path.join()' normalizes traversal sequences like '../', an attacker can escape the designated temporary directory. This allows for arbitrary file creation at attacker-controlled locations with the privileges of the Node.js process. The vulnerability is fixed in version 0.2.6.
Affected products
- raszi tmp < 0.2.6
Identifiers
- CVE-2026-44705
- GHSA-ph9p-34f9-6g65
Timeline
- 2026-05-26: advisory: GitHub Security Advisory published
- 2026-06-11: disclosed: NVD publication date
- 2026-06-11: patched: Fix released in version 0.2.6