Skip to content
VulniPulse
Critical 1 vendor · 1 advisory

CVE-2025-68146: filelock has TOCTOU race condition that allows symlink attacks during lock file creation

CVE-2025-68146 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H · base score 6.3, scored by GitHub_MAttack vector: local. Attack complexity: high. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
  • CWE-59: Improper Link Resolution Before File Access ('Link Following')
  • CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
EPSS
0.21% chance of exploitation in the next 30 days (11th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Vendor advisories
1 from Splunk
Assigned by
GitHub_M (CNA)
CVE record published
Listed by VulniPulse

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2025-68146; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

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.

Text from the CVE.org record (GitHub_M).

Vendor advisories for CVE-2025-68146

Splunk

1 advisory
  • Advisory severityCritical

    Critical [CVE-2022-40897 +57] Third-Party Package Updates in Splunk SOAR - November 2026

    SVD-2026-1109Source published

    This bulletin covers 58 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk SOAR version 8.8.0, and higher. Affected product named by the advisory: Splunk SOAR 8.8.

    Affected products in this advisory
    • Splunk SOAR 8.8
    Source-reported affected versions
    • Splunk SOAR Below 8.8.0
    Source-reported fixed versions
    • Splunk SOAR 8.8.0
    Mitigation guidance
    • Upgrade Splunk SOAR to version 8.8.0, or higher.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All Splunk advisories

Get an email when Splunk publishes the next one.

See Splunk's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Splunk