Improper Locking Affecting datahub-ingestion-fips package, versions <1.8.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.16% (5th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-DATAHUBINGESTIONFIPS-21751379
  • published27 Oct 2026
  • disclosed5 Nov 2026

Introduced: 27 Oct 2026

NewCVE-2026-112907  (opens in a new tab)
CWE-667  (opens in a new tab)

How to fix?

Upgrade Chainguard datahub-ingestion-fips to version 1.8.0-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream datahub-ingestion-fips package and not the datahub-ingestion-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. This issue is fixed in version 4.2.1.