bcrypt-3.0.8.tgz: 7 vulnerabilities (highest severity is: 8.8) reachable

[mend-for-github-com]

Vulnerable Library - bcrypt-3.0.8.tgz

A bcrypt library for NodeJS.

Library home page: https://registry.npmjs.org/bcrypt/-/bcrypt-3.0.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/bcrypt/package.json

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Vulnerabilities

Vulnerability	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (bcrypt version)	Remediation Possible**	Reachability
CVE-2020-7689	Medium	5.9	Not Defined	0.1%	bcrypt-3.0.8.tgz	Direct	bcrypt - 5.0.0	❌	Reachable
CVE-2026-23950	High	8.8	Not Defined	0.0%	tar-4.4.19.tgz	Transitive	6.0.0	✅	Unreachable
CVE-2026-23745	High	7.1	Not Defined	0.0%	tar-4.4.19.tgz	Transitive	N/A*	❌	Unreachable
CVE-2024-28863	Medium	6.5	Not Defined	0.4%	tar-4.4.19.tgz	Transitive	N/A*	❌	Unreachable
CVE-2026-24842	High	8.2	Not Defined	0.0%	tar-4.4.19.tgz	Transitive	6.0.0	✅
CVE-2026-26996	High	7.5	Not Defined		minimatch-3.1.2.tgz	Transitive	5.0.1	✅
CVE-2026-26960	High	7.1	Not Defined		tar-4.4.19.tgz	Transitive	6.0.0	✅

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2020-7689

Vulnerable Library - bcrypt-3.0.8.tgz

A bcrypt library for NodeJS.

Library home page: https://registry.npmjs.org/bcrypt/-/bcrypt-3.0.8.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/bcrypt/package.json

Dependency Hierarchy:

• ❌ bcrypt-3.0.8.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Reachability Analysis

This vulnerability is potentially reachable

dvna-0.0.1/core/authHandler.js (Application)
  -> ❌ bcrypt-3.0.8/bcrypt.js (Vulnerable Component)

Vulnerability Details

Data is truncated wrong when its length is greater than 255 bytes.

Publish Date: 2020-07-01

URL: CVE-2020-7689

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.1%

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-5wg4-74h6-q47v

Release Date: 2020-07-01

Fix Resolution: bcrypt - 5.0.0

CVE-2026-23950

Vulnerable Library - tar-4.4.19.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/node-pre-gyp/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • ❌ tar-4.4.19.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the "path-reservations" system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., "ß" and "ss"), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a "PathReservations" system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using "NFD" Unicode normalization (in which "ß" and "ss" are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which "ß" causes an inode collision with "ss")). This enables an attacker to circumvent internal parallelization locks ("PathReservations") using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates "path-reservations.js" to use a normalization form that matches the target filesystem's behavior (e.g., "NFKD"), followed by first "toLocaleLowerCase('en')" and then "toLocaleUpperCase('en')". As a workaround, users who cannot upgrade promptly, and who are programmatically using "node-tar" to extract arbitrary tarball data should filter out all "SymbolicLink" entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Publish Date: 2026-01-20

URL: CVE-2026-23950

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

CVSS 3 Score Details (8.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: High
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-r6q2-hw4h-h46w

Release Date: 2026-01-20

Fix Resolution (tar): 7.5.4

Direct dependency fix Resolution (bcrypt): 6.0.0

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2026-23745

Vulnerable Library - tar-4.4.19.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/node-pre-gyp/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • ❌ tar-4.4.19.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.

Publish Date: 2026-01-16

URL: CVE-2026-23745

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

CVSS 3 Score Details (7.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-01-16

Fix Resolution: https://github.com/isaacs/node-tar.git - v7.5.3

CVE-2024-28863

Vulnerable Library - tar-4.4.19.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/node-pre-gyp/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • ❌ tar-4.4.19.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running node-tar and even crash the Node.js client within few seconds of running it using a path with too many sub-folders inside. Version 6.2.1 fixes this issue by preventing extraction in excessively deep sub-folders.

Publish Date: 2024-03-21

URL: CVE-2024-28863

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.4%

CVSS 3 Score Details (6.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-f5x3-32g6-xq36

Release Date: 2024-03-21

Fix Resolution: tar - 6.2.1

CVE-2026-24842

Vulnerable Library - tar-4.4.19.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/node-pre-gyp/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • ❌ tar-4.4.19.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Vulnerability Details

node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory. Version 7.5.7 contains a fix for the issue.

Publish Date: 2026-01-28

URL: CVE-2026-24842

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

CVSS 3 Score Details (8.2)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-01-28

Fix Resolution (tar): 7.5.7

Direct dependency fix Resolution (bcrypt): 6.0.0

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2026-26996

Vulnerable Library - minimatch-3.1.2.tgz

a glob matcher in javascript

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/minimatch/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • rimraf-2.7.1.tgz
      • glob-7.2.3.tgz
        • ❌ minimatch-3.1.2.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This issue has been fixed in version 10.2.1.

Publish Date: 2026-02-20

URL: CVE-2026-26996

Threat Assessment

Exploit Maturity: Not Defined

EPSS:

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-3ppc-4f35-3m26

Release Date: 2026-02-19

Fix Resolution (minimatch): 10.2.1

Direct dependency fix Resolution (bcrypt): 5.0.1

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2026-26960

Vulnerable Library - tar-4.4.19.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/node-pre-gyp/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-3.0.8.tgz (Root Library)
  • node-pre-gyp-0.14.0.tgz
    • ❌ tar-4.4.19.tgz (Vulnerable Library)

Found in HEAD commit: d2708792be12ec4955aee513fffe301dcfefc7d8

Found in base branch: master

Vulnerability Details

node-tar is a full-featured Tar for Node.js. When using default options in versions 7.5.7 and below, an attacker-controlled archive can create a hardlink inside the extraction directory that points to a file outside the extraction root, enabling arbitrary file read and write as the extracting user. Severity is high because the primitive bypasses path protections and turns archive extraction into a direct filesystem access primitive. This issue has been fixed in version 7.5.8.

Publish Date: 2026-02-20

URL: CVE-2026-26960

Threat Assessment

Exploit Maturity: Not Defined

EPSS:

CVSS 3 Score Details (7.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-02-18

Fix Resolution (tar): 7.5.8

Direct dependency fix Resolution (bcrypt): 6.0.0

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.