An update for python-filelock is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-3143 Final 1.0 1.0 2026-07-24 Initial 2026-07-24 2026-07-24 openEuler SA Tool V1.0 2026-07-24 python-filelock security update An update for python-filelock is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4 Security Fix(es): 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.(CVE-2025-68146) An update for python-filelock is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium python-filelock https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3143 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2025-68146 https://nvd.nist.gov/vuln/detail/CVE-2025-68146 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 openEuler-24.03-LTS-SP4 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 python-filelock-3.13.1-5.oe2403sp1.src.rpm python-filelock-3.13.1-5.oe2403sp3.src.rpm python-filelock-3.13.1-5.oe2403sp4.src.rpm python-filelock-3.0.12-2.oe2003sp4.src.rpm python-filelock-3.0.12-4.oe2203sp4.src.rpm python-filelock-doc-3.13.1-5.oe2403sp1.noarch.rpm python-filelock-help-3.13.1-5.oe2403sp1.noarch.rpm python3-filelock-3.13.1-5.oe2403sp1.noarch.rpm python-filelock-doc-3.13.1-5.oe2403sp3.noarch.rpm python-filelock-help-3.13.1-5.oe2403sp3.noarch.rpm python3-filelock-3.13.1-5.oe2403sp3.noarch.rpm python-filelock-doc-3.13.1-5.oe2403sp4.noarch.rpm python-filelock-help-3.13.1-5.oe2403sp4.noarch.rpm python3-filelock-3.13.1-5.oe2403sp4.noarch.rpm python-filelock-doc-3.0.12-2.oe2003sp4.noarch.rpm python-filelock-help-3.0.12-2.oe2003sp4.noarch.rpm python3-filelock-3.0.12-2.oe2003sp4.noarch.rpm python-filelock-doc-3.0.12-4.oe2203sp4.noarch.rpm python-filelock-help-3.0.12-4.oe2203sp4.noarch.rpm python3-filelock-3.0.12-4.oe2203sp4.noarch.rpm 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. 2026-07-24 CVE-2025-68146 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 openEuler-24.03-LTS-SP4 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 Medium 6.5 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H python-filelock security update 2026-07-24 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3143