CVE-2026-59873 critical vulnerability
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Could you please correct the following critical vulnerability :
redis/redisinsight:3.8.0 (alpine 3.23.3)
Report Summary
| Target | Type | Vulnerabilities | Secrets |
|---|---|---|---|
| usr/local/lib/node_modules/npm/node_modules/cacache/node_modules/tar/package.json | node-pkg | 1 | - |
| usr/local/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json | node-pkg | 1 | - |
Node.js (node-pkg)
Total: 3 (CRITICAL: 3)
| Library | Vulnerability | Severity | Status | Installed Version | Fixed Version | Title |
|---|---|---|---|---|---|---|
| tar (package.json) | CVE-2026-59873 | CRITICAL | fixed | 6.2.1 7.4.3 |
7.5.19 | tar: node-tar: Denial of Service via crafted gzip bomb https://avd.aquasec.com/nvd/cve-2026-59873 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the dependency manifests or lockfiles that produce the listed npm paths under usr/local/lib/node_modules/npm/node_modules. Trace the vulnerable tar dependency and update it to the reported fixed version 7.5.19, then run the repository's dependency or image vulnerability scan to confirm CVE-2026-59873 is no longer reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100