https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:49:34 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/euvd-2026-257989 EUVD-2026-257989 https://cve.radiocsirt.org/vuln/euvd-2026-257989 https://cve.radiocsirt.org/vuln/fkie_cve-2025-54798 <p>tmp is a temporary file and directory creator for node.js. In versions 0.2.3 and below, tmp is vulnerable to an arbitrary temporary file / directory write via symbolic link dir parameter. This is fixed in version 0.2.4.</p> <p>tmp is a temporary file and directory creator for node.js. In versions 0.2.3 and below, tmp is vulnerable to an arbitrary temporary file / directory write via symbolic link dir parameter. This is fixed in version 0.2.4.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-54798 https://cve.radiocsirt.org/vuln/ghsa-52f5-9888-hmc6 <p><strong>Affected:</strong> npm: tmp</p> <p>### Summary</p> <p>`tmp@0.2.3` is vulnerable to an Arbitrary temporary file / directory write via symbolic link `dir` parameter.</p> <p>### Details</p> <p>According to the documentation there are some conditions that must be held:</p> <p>``` // https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L41-L50</p> <p>Other breaking changes, i.e.</p> <p>- template must be relative to tmpdir - name must be relative to tmpdir - dir option must be relative to tmpdir //&lt;-- this assumption can be bypassed using symlinks</p> <p>are still in place.</p> <p>In order to override the system&#39;s tmpdir, you will have to use the newly introduced tmpdir option.</p> <p>// https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L375 * `dir`: the optional temporary directory that must be relative to the system&#39;s default temporary directory. absolute paths are fine as long as they point to a location under the system&#39;s default temporary directory. Any directories along the so specified path must exist, otherwise a ENOENT error will be thrown upon access, as tmp will not check the availability of the path, nor will it establish the requested path for you. ```</p> <p>Related issue: https://github.com/raszi/node-tmp/issues/207.</p> <p>The issue occurs because `_resolvePath` does not properly handle symbolic link when resolving paths: ```js // https://github.com/raszi/node-tmp/blob/v0.2.3/lib/tmp.js#L573-L579 function _resolvePath(name, tmpDir) { if (name.startsWith(tmpDir)) { return path.resolve(name); } else { return p…</p> <p><strong>Affected:</strong> npm: tmp</p> <p>### Summary</p> <p>`tmp@0.2.3` is vulnerable to an Arbitrary temporary file / directory write via symbolic link `dir` parameter.</p> <p>### Details</p> <p>According to the documentation there are some conditions that must be held:</p> <p>``` // https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L41-L50</p> <p>Other breaking changes, i.e.</p> <p>- template must be relative to tmpdir - name must be relative to tmpdir - dir option must be relative to tmpdir //&lt;-- this assumption can be bypassed using symlinks</p> <p>are still in place.</p> <p>In order to override the system&#39;s tmpdir, you will have to use the newly introduced tmpdir option.</p> <p>// https://github.com/raszi/node-tmp/blob/v0.2.3/README.md?plain=1#L375 * `dir`: the optional temporary directory that must be relative to the system&#39;s default temporary directory. absolute paths are fine as long as they point to a location under the system&#39;s default temporary directory. Any directories along the so specified path must exist, otherwise a ENOENT error will be thrown upon access, as tmp will not check the availability of the path, nor will it establish the requested path for you. ```</p> <p>Related issue: https://github.com/raszi/node-tmp/issues/207.</p> <p>The issue occurs because `_resolvePath` does not properly handle symbolic link when resolving paths: ```js // https://github.com/raszi/node-tmp/blob/v0.2.3/lib/tmp.js#L573-L579 function _resolvePath(name, tmpDir) { if (name.startsWith(tmpDir)) { return path.resolve(name); } else { return p…</p> https://cve.radiocsirt.org/vuln/ghsa-52f5-9888-hmc6 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15502-1 <p>jupyter-nbdime-7.0.2-23.1 on GA media</p> <p>jupyter-nbdime-7.0.2-23.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15502-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-54798 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-tmp, Ubuntu:18.04:LTS: node-tmp, Ubuntu:20.04:LTS: node-tmp, Ubuntu:22.04:LTS: node-tmp, Ubuntu:24.04:LTS: node-tmp, Ubuntu:25.10: node-tmp, Ubuntu:26.04:LTS: node-tmp</p> <p>tmp is a temporary file and directory creator for node.js. In versions 0.2.3 and below, tmp is vulnerable to an arbitrary temporary file / directory write via symbolic link dir parameter. This is fixed in version 0.2.4.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-tmp, Ubuntu:18.04:LTS: node-tmp, Ubuntu:20.04:LTS: node-tmp, Ubuntu:22.04:LTS: node-tmp, Ubuntu:24.04:LTS: node-tmp, Ubuntu:25.10: node-tmp, Ubuntu:26.04:LTS: node-tmp</p> <p>tmp is a temporary file and directory creator for node.js. In versions 0.2.3 and below, tmp is vulnerable to an arbitrary temporary file / directory write via symbolic link dir parameter. This is fixed in version 0.2.4.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-54798 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0778 <p>Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway Policy Manager ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway Policy Manager ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0778