How severe is CVE-2025-64118?

CVE-2025-64118 has a CVSS 4.0 base score of 6.1, rated medium severity.

Is CVE-2025-64118 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-64118?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-64118 have an EU (EUVD) identifier?

Yes. CVE-2025-64118 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37034.

When was CVE-2025-64118 published?

CVE-2025-64118 was published on 2025-10-30 and last updated on 2026-06-17.

CVE-2025-64118

CVE-2025-64118 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: Medium (CVSS 4.0 base score 6.1)
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-37034
Weakness: CWE-362
Published: 2025-10-30
Last modified: 2026-06-17

Description

node-tar is a Tar for Node.js. In 7.5.1, using .t (aka .list) with { sync: true } to read tar entry contents returns uninitialized memory contents if tar file was changed on disk to a smaller size while being read. This vulnerability is fixed in 7.5.2.

Frequently asked questions

What is CVE-2025-64118?: node-tar is a Tar for Node.js. In 7.5.1, using .t (aka .list) with { sync: true } to read tar entry contents returns uninitialized memory contents if tar file was changed on disk to a smaller size while being read. This vulnerability is fixed in 7.5.2.
How severe is CVE-2025-64118?: CVE-2025-64118 has a CVSS 4.0 base score of 6.1, rated medium severity.
Is CVE-2025-64118 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-64118?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-64118 have an EU (EUVD) identifier?: Yes. CVE-2025-64118 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37034.
When was CVE-2025-64118 published?: CVE-2025-64118 was published on 2025-10-30 and last updated on 2026-06-17.

References

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →