bcrypt-5.1.1.tgz: 3 vulnerabilities (highest severity is: 8.8)

[mend-bolt-for-github]

Vulnerable Library - bcrypt-5.1.1.tgz

Path to dependency file: /blockchain_integration/pi_network/smartship/package.json

Path to vulnerable library: /blockchain_integration/pi_network/PiSure/client/node_modules/tar/package.json,/blockchain_integration/pi_network/smartship/node_modules/tar/package.json,/blockchain_integration/pi_network/pi-browser-app/node_modules/tar/package.json

Found in HEAD commit: 011e5f9d5ce310049a1a68c19f7df65be4f88caf

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (bcrypt version)	Remediation Possible**
CVE-2026-23950	High	8.8	tar-6.2.1.tgz	Transitive	6.0.0	❌
CVE-2026-24842	High	8.2	tar-6.2.1.tgz	Transitive	6.0.0	❌
CVE-2026-23745	High	7.1	tar-6.2.1.tgz	Transitive	N/A*	❌

*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-2026-23950

Vulnerable Library - tar-6.2.1.tgz

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

Path to dependency file: /blockchain_integration/pi_network/PiSure/client/package.json

Path to vulnerable library: /blockchain_integration/pi_network/PiSure/client/node_modules/tar/package.json,/blockchain_integration/pi_network/smartship/node_modules/tar/package.json,/blockchain_integration/pi_network/pi-browser-app/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-5.1.1.tgz (Root Library)
  • node-pre-gyp-1.0.11.tgz
    • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 011e5f9d5ce310049a1a68c19f7df65be4f88caf

Found in base branch: main

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

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

Step up your Open Source Security Game with Mend here

CVE-2026-24842

Vulnerable Library - tar-6.2.1.tgz

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

Path to dependency file: /blockchain_integration/pi_network/PiSure/client/package.json

Path to vulnerable library: /blockchain_integration/pi_network/PiSure/client/node_modules/tar/package.json,/blockchain_integration/pi_network/smartship/node_modules/tar/package.json,/blockchain_integration/pi_network/pi-browser-app/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-5.1.1.tgz (Root Library)
  • node-pre-gyp-1.0.11.tgz
    • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 011e5f9d5ce310049a1a68c19f7df65be4f88caf

Found in base branch: main

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

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

Step up your Open Source Security Game with Mend here

CVE-2026-23745

Vulnerable Library - tar-6.2.1.tgz

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

Path to dependency file: /blockchain_integration/pi_network/PiSure/client/package.json

Path to vulnerable library: /blockchain_integration/pi_network/PiSure/client/node_modules/tar/package.json,/blockchain_integration/pi_network/smartship/node_modules/tar/package.json,/blockchain_integration/pi_network/pi-browser-app/node_modules/tar/package.json

Dependency Hierarchy:

• bcrypt-5.1.1.tgz (Root Library)
  • node-pre-gyp-1.0.11.tgz
    • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 011e5f9d5ce310049a1a68c19f7df65be4f88caf

Found in base branch: main

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

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

Step up your Open Source Security Game with Mend here