CVE-2026-59874
node-tar bug allows crafted tar to hang parser, causing denial-of-service.
Is CVE-2026-59874 being exploited?
Not confirmed. CVE-2026-59874 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-59874?
CVE-2026-59874 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59874?
Yes. A fix has been recorded for CVE-2026-59874. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59874 affect?
CVE-2026-59874 affects node-tar < 7.5.18, Node.js applications using node-tar, npm packages bundling node-tar. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59874?
Upgrade node-tar to >=7.5.18 and validate untrusted archives before parsing.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Denial of Service: a negative base-256 encoded size in a tar header causes the parser to loop and stall processing, enabling resource exhaustion when untrusted archives are processed.
Patch when possible
- affected< 7.5.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.