GHSA-69hj-f68j-2879

filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path

Medium highest severity reported · also known as CVE-2026-112909

5
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.2%
EPSS for CVE-2026-112909, percentile 13

Catalog tools matching GHSA-69hj-f68j-2879

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
cartography
Cloud Security
0.144.0filelock@3.32.7
pypi
4.2.1not analyzeduv.lockDispute
prowler
Cloud Security
5.47.0filelock@3.20.3
pypi
4.2.1not analyzedapi/uv.lockDispute
cloudsplaining
Cloud Security
0.9.1filelock@3.29.0
pypi
4.2.1not analyzeduv.lockDispute
semgrep
Static Application Security Testing (SAST) › Multi-language
v1.183.0filelock@4.0.6
pypi
4.2.1not analyzedscripts/release/uv.lockDispute
detect-secrets
Pre-commit & Secrets Detection
v1.5.0filelock@3.13.1
pypi
4.2.1not analyzedrequirements-dev.txtDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-69hj-f68j-2879 · NVD CVE-2026-112909 · OSV GHSA-69hj-f68j-2879

Grype data sources: https://github.com/advisories/GHSA-69hj-f68j-2879