CVE-2026-59873
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditednode-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to exhaust disk space and CPU. This issue is fixed in version 7.5.19.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencenode-tar before 7.5.19 lacks hard upper bounds on decompressed data size, entry counts, and decompression ratio in extraction paths (src/extract.ts), allowing attackers to embed small gzip bombs in tar archives that expand to enormous sizes during extraction, exhausting disk space and CPU.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.5.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate node-tar in your project dependenciesCheck package.json for node-tar in dependencies, or run 'npm ls node-tar' to see installed packagesAffected if node-tar is listed as a dependency with version lower than 7.5.19
-
Verify the installed node-tar versionRun 'npm list node-tar' or check node_modules/node-tar/package.json for the version fieldAffected if The installed version is below 7.5.19
-
Identify if extraction functionality is usedSearch your codebase for calls to tar.extract(), tar.Extract, or unpack methods from the node-tar moduleAffected if Your code calls extraction methods from node-tar to unpack tar archives from untrusted sources
-
Check for custom size limit enforcementReview your extraction code for options like maxSize, maxFiles, or similar limit parameters passed to extraction methodsAffected if No size or count limits are enforced on extracted content and the node-tar version is below 7.5.19
Your environment is affected if node-tar below version 7.5.19 is installed and your application uses its extraction functionality to unpack tar archives, especially from untrusted sources, without additional size limits.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.5.19
Upgrade node-tar to version 7.5.19 or later to enforce bounds checking on decompression and prevent resource exhaustion from crafted archives.
node-tar version 7.5.19 or later
- Check the current version of node-tar in use (e.g., run `npm list tar` or inspect package.json)
- Update the node-tar dependency to version 7.5.19 or later in package.json
- Run `npm install` to install the updated version
- Verify the upgrade was successful by running `npm list tar` to confirm the installed version
- Run existing tests to ensure the upgrade does not break functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data