BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-54798High confidence

tmp does not restrict arbitrary temporary file / directory write via symbolic link `dir` parameter

raszi · node-tmp

Official source article: GitHub GHSA-52F5-9888-HMC6 ↗. Check the applicable product and release in the original source.

2.5LowCVSS 3.1
Recommended action
Within 7 days

Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.34% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs raszi node-tmp and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-tmpVendor fix publishedDebian records a fixed source-package version for this release.0.2.2+dfsg+~0.2.3-1.1~deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-tmpVendor fix publishedDebian records a fixed source-package version for this release.0.2.2+dfsg+~0.2.3-1.1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-tmpVendor fix publishedDebian records a fixed source-package version for this release.0.2.2+dfsg+~0.2.3-1.1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-tmpVendor fix publishedDebian records a fixed source-package version for this release.0.2.2+dfsg+~0.2.3-1.1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-tmpUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmtmp<= 0.2.30.2.4GitHub advisory ↗upstream repository advisory · 3 Nov 2025
npmtmpSEMVER: introduced 0; fixed 0.2.40.2.4OSV record ↗aggregator derived · 10 Sep 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-23895

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

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.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

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.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Improper Link Resolution Before File Access ('Link Following') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following'). 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-59Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0778Dell Secure Connect Gateway Policy Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway Policy Manager ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0606Multiples vulnérabilités dans les produits IBM

cord?id=CVE-2025-3633 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-48976 https://www.cve.org/CVERecord?id=CVE-2025-48976 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-50182 https://www.cve.org/CVERecord?id=CVE-2025-50182 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54798 https://www.cve.org/CVERecord?id=CVE-2025-54798 Référence CVE CVE-2025-56200 https://www.cve.org/CVERecord?id=CVE-2025-56200 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-6020 https://www.cve.org/CVERecord?id=CVE-2025-6020 Référence CVE CVE-2025-68146 https://www.cve.org/CVERecord?id=CVE-2025-68146 Référence CVE CVE-2025-7207 https://www.cve.org/CVERecord?id=CVE-2025-7207 Référence CVE CVE-2025-7962 https://www.cve.org/CVERecord?id=CVE-2025-7962 Référence CVE CVE-2026-1188 https://www.cve.org/CVERecord?id=CVE-2026-1188 Gestion détaillée du document le 15 mai 2026 Version initiale Alertes Av

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1137Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-21587 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-29927 https://www.cve.org/CVERecord?id=CVE-2025-29927 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-47279 https://www.cve.org/CVERecord?id=CVE-2025-47279 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54798 https://www.cve.org/CVERecord?id=CVE-2025-54798 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-55182 https://www.cve.org/CVERecord?id=CVE-2025-55182 Référence CVE CVE-2025-55183 https://www.cve.org/CVERecord?id=CVE-2025-55183 Référence CVE CVE-2025-55184 https://www.cve.org/CVERecord?id=CVE-2025-55184 Référence CVE CVE-2025-57752 https://www.cve.org/CVERecord?id=CVE-2025-57752 Référence CVE CVE-2025-57822 https://www.cve.org/CVERecord?id=CVE-2025-57822 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-50106 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-52434 https://www.cve.org/CVERecord?id=CVE-2025-52434 Référence CVE CVE-2025-53023 https://www.cve.org/CVERecord?id=CVE-2025-53023 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53506 https://www.cve.org/CVERecord?id=CVE-2025-53506 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-54798 https://www.cve.org/CVERecord?id=CVE-2025-54798 Référence CVE CVE-2025-55193 https://www.cve.org/CVERecord?id=CVE-2025-55193 Référence CVE CVE-2025-55248 https://www.cve.org/CVERecord?id=CVE-2025-55248 Référence CVE CVE-2025-55315 https://www.cve.org/CVERecord?id=CVE-2025-55315 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55754 https://www.cve.org/CVERecord?id=CVE-2025-55754 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-58446 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-016909KARASZI Istvan の Node.js 用 Tmp におけるリンク解釈に関する脆弱性

KARASZI Istvan の Node.js 用 Tmp には、リンク解釈に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
node-tmp: < 0.2.4
Fixed
0.2.4.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 7 Aug 2025 · Last source change 3 Nov 2025, 20:06 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-23895
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-54798 · cve.blacktree.nl