Process-memory disclosure via truncated synchronous archive read
Published Oct 30, 2025 · Updated Oct 30, 2025
Information disclosure in isaacs tar 7.5.1 allows local users to read process memory by truncating a synchronously listed archive. In listFileSync, Buffer.allocUnsafe reserves the stat-reported size, but fs.readSync can fill less after truncation and the parser receives the entire buffer. Exploitation requires Node.js 22 or 25.1 and later, sync:true, onReadEntry body handling, and a boundary-timed truncation; larger archives instead hang.
Summary
What happened
Information disclosure in isaacs tar 7.5.1 allows local users to read process memory by truncating a synchronously listed archive. In listFileSync, Buffer.allocUnsafe reserves the stat-reported size, but fs.readSync can fill less after truncation and the parser receives the entire buffer. Exploitation requires Node.js 22 or 25.1 and later, sync:true, onReadEntry body handling, and a boundary-timed truncation; larger archives instead hang.
The record
- CVE
- CVE-2025-64118
- Published
- Oct 30, 2025
- Updated
- Oct 30, 2025
- Vendor
- isaacs
- Product
- tar
- Classifications
- CWE-362, CWE-367, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 30, 2025CVE publishedPublication date reported by the CVE source.
- Oct 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 7.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream synchronous list race proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo