huggingface_hub-0.24.7-py3-none-any.whl: 2 vulnerabilities (highest severity is: 6.3) unreachable

[mend-for-github-com]

Vulnerable Library - huggingface_hub-0.24.7-py3-none-any.whl

Path to dependency file: /requirements.txt

Path to vulnerable library: /tmp/ws-ua_20260219120409_AEEMWL/python_IKDEBG/20260219120410/filelock-3.19.1-py3-none-any.whl

Found in HEAD commit: c2a0de4212c13487918a46a2935ca84031dd91aa

Vulnerabilities

Vulnerability	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (huggingface_hub version)	Remediation Possible**	Reachability
CVE-2025-68146	Medium	6.3	Not Defined	0.0%	filelock-3.19.1-py3-none-any.whl	Transitive	N/A*	❌	Unreachable
CVE-2026-22701	Medium	5.3	Not Defined	0.0%	filelock-3.19.1-py3-none-any.whl	Transitive	0.25.0	✅	Unreachable

*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-2025-68146

Vulnerable Library - filelock-3.19.1-py3-none-any.whl

A platform independent file lock.

Library home page: https://files.pythonhosted.org/packages/42/14/42b2651a2f46b022ccd948bca9f2d5af0fd8929c4eec235b8d6d844fbe67/filelock-3.19.1-py3-none-any.whl

Path to dependency file: /requirements.txt

Path to vulnerable library: /tmp/ws-ua_20260219120409_AEEMWL/python_IKDEBG/20260219120410/filelock-3.19.1-py3-none-any.whl

Dependency Hierarchy:

• huggingface_hub-0.24.7-py3-none-any.whl (Root Library)
  • ❌ filelock-3.19.1-py3-none-any.whl (Vulnerable Library)

Found in HEAD commit: c2a0de4212c13487918a46a2935ca84031dd91aa

Found in base branch: main

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

filelock is a platform-independent file lock for Python. In versions prior to 3.20.1, a Time-of-Check-Time-of-Use (TOCTOU) race condition allows local attackers to corrupt or truncate arbitrary user files through symlink attacks. The vulnerability exists in both Unix and Windows lock file creation where filelock checks if a file exists before opening it with O_TRUNC. An attacker can create a symlink pointing to a victim file in the time gap between the check and open, causing os.open() to follow the symlink and truncate the target file. All users of filelock on Unix, Linux, macOS, and Windows systems are impacted. The vulnerability cascades to dependent libraries. The attack requires local filesystem access and ability to create symlinks (standard user permissions on Unix; Developer Mode on Windows 10+). Exploitation succeeds within 1-3 attempts when lock file paths are predictable. The issue is fixed in version 3.20.1. If immediate upgrade is not possible, use SoftFileLock instead of UnixFileLock/WindowsFileLock (note: different locking semantics, may not be suitable for all use cases); ensure lock file directories have restrictive permissions (chmod 0700) to prevent untrusted users from creating symlinks; and/or monitor lock file directories for suspicious symlinks before running trusted applications. These workarounds provide only partial mitigation. The race condition remains exploitable. Upgrading to version 3.20.1 is strongly recommended.

Publish Date: 2025-12-16

URL: CVE-2025-68146

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

CVSS 3 Score Details (6.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2025-12-16

Fix Resolution: filelock - 3.20.1

CVE-2026-22701

Vulnerable Library - filelock-3.19.1-py3-none-any.whl

A platform independent file lock.

Library home page: https://files.pythonhosted.org/packages/42/14/42b2651a2f46b022ccd948bca9f2d5af0fd8929c4eec235b8d6d844fbe67/filelock-3.19.1-py3-none-any.whl

Path to dependency file: /requirements.txt

Path to vulnerable library: /tmp/ws-ua_20260219120409_AEEMWL/python_IKDEBG/20260219120410/filelock-3.19.1-py3-none-any.whl

Dependency Hierarchy:

• huggingface_hub-0.24.7-py3-none-any.whl (Root Library)
  • ❌ filelock-3.19.1-py3-none-any.whl (Vulnerable Library)

Found in HEAD commit: c2a0de4212c13487918a46a2935ca84031dd91aa

Found in base branch: main

Reachability Analysis

The vulnerable code is unreachable

Vulnerability Details

filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

Publish Date: 2026-01-10

URL: CVE-2026-22701

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

CVSS 3 Score Details (5.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-01-10

Fix Resolution (filelock): 3.20.3

Direct dependency fix Resolution (huggingface-hub): 0.25.0

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.