Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7amended

tmp has Path Traversal via unsanitized prefix/postfix that enables directory escape

CVE-2026-44705GHSA-ph9p-34f9-6g65

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tmp 0.2.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm tmp

    Affected
    < 0.2.6
    Fixed in
    0.2.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-44705: 0.43% estimated exploitation activity in the next 30 days; percentile 37.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Details Root Cause: The vulnerability exists in tmp's path construction logic where user-supplied options are directly concatenated into file paths without sanitization or validation. Technical Flow: 1. Filename Construction: tmp builds filenames as <prefix-<pid-<random-<postfix 2. Path Composition: Final path computed as path.join(tmpDir, opts.dir, name) 3. Path Normalization: Node.js path.join()…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-ph9p-34f9-6g65

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-ph9p-34f9-6g65

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44705

Advisory: tmp has Path Traversal via unsanitized prefix/postfix that enables directory escape
IDs: CVE-2026-44705, GHSA-ph9p-34f9-6g65
Record: https://patchnext.com/advisories/cve-2026-44705 (revision 3, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tmp 0.2.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tmp: affected < 0.2.6; fixed in 0.2.6

## Suggested inspection (read-only)
- `npm ls tmp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tmp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-ph9p-34f9-6g65 (OSV record GHSA-ph9p-34f9-6g65 lists affected ranges: npm tmp >=0 <0.2.6 (fixed))
- Verified: https://github.com/advisories/GHSA-ph9p-34f9-6g65 (GitHub-reviewed advisory GHSA-ph9p-34f9-6g65 lists affected ranges: npm tmp >=0 <0.2.6)

Commands are suggestions: review each one before running it.

Loading voting…