← Back
CVE-2025-68146
Vulnerability in filelock (CVE-2025-68146)
Summary
vulnerability in filelock (CVE-2025-68146). Data can be tampered with by attackers. Exploitable via ``O_NOFOLLOW``. Mitigation: upgrade to `3.20.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-68146** has been found in filelock.
Attackers can target a specific entry point like ``O_NOFOLLOW`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade filelock to **3.20.1** or later.
If unsure, ask your IT team or search "filelock CVE-2025-68146" on the vendor's site.
CVE-2025-68146 (filelock) — CWE-362 /
Attack vector: local / no user interaction
Attack surface: `O_NOFOLLOW` / `filelock_simple_poc.py` / `weaponized_virtualenv.py` / `weaponized_pytorch.py`
Patched: `3.20.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-362) exists in filelock. Attackers reach the vulnerable code path via ``O_NOFOLLOW`` without authentication.
📍 Affected scope
filelock — . Attack surface: `O_NOFOLLOW` / `filelock_simple_poc.py` / `weaponized_virtualenv.py` / `weaponized_pytorch.py`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **3.20.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'filelock' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'filelock' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `filelock` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade filelock to 3.20.1ステージング環境で 3.20.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
filelock
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.20.1"}]}]
References
- advisory https://github.com/advisories/GHSA-w853-jp5j-5j7f
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-68146
- package https://github.com/tox-dev/filelock
- package https://pypi.org/project/filelock
- web https://github.com/tox-dev/filelock/security/advisories/GHSA-w853-jp5j-5j7f
- web https://github.com/tox-dev/filelock/commit/4724d7f8c3393ec1f048c93933e6e3e6ec321f0e
- web https://github.com/tox-dev/filelock/releases/tag/3.20.1
- web https://learn.microsoft.com/en-us/windows/win32/fileio/file-attribute-constants
- web https://pubs.opengroup.org/onlinepubs/9699919799/functions/open.html