Search

Find a vulnerability

Search criteria ⓘ Use this form to refine search results.
Full-text search supports keyword queries with ranking and filtering.
You can combine vendor, product, and sources to narrow results.
Enable “Apply ordering” to sort by date instead of relevance.

    7 vulnerabilities found for python-filelock by azure linux

    AZL-112711 (CVE-2026-112910)

    Vulnerability from osv_azurelinux – Published: 2026-11-05 22:17 – Updated: 2026-11-16 05:30 – Source website
    VLAI
    Summary
    CVE-2026-112910 affecting package python-filelock 3.20.3-4
    Details

    filelock is a platform-independent file lock for Python. From 3.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory's inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. This issue is fixed in version 4.2.1.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: ≤ 3.20.3-4 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "3.20.3-4"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "filelock is a platform-independent file lock for Python. From 3.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory\u0027s inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. This issue is fixed in version 4.2.1.",
      "id": "AZL-112711",
      "modified": "2026-11-16T05:30:07Z",
      "published": "2026-11-05T22:17:46Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112910"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-112910 affecting package python-filelock 3.20.3-4",
      "upstream": [
        "CVE-2026-112910"
      ]
    }

    AZL-110070 (CVE-2026-112935)

    Vulnerability from osv_azurelinux – Published: 2026-10-20 15:17 – Updated: 2026-11-18 05:33 – Source website
    VLAI
    Summary
    CVE-2026-112935 affecting package python-filelock 3.20.3-4
    Details

    filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: ≤ 3.20.3-4 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "3.20.3-4"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor\u0027s modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.",
      "id": "AZL-110070",
      "modified": "2026-11-18T05:33:41Z",
      "published": "2026-10-20T15:17:16Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112935"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-112935 affecting package python-filelock 3.20.3-4",
      "upstream": [
        "CVE-2026-112935"
      ]
    }

    AZL-110067 (CVE-2026-112909)

    Vulnerability from osv_azurelinux – Published: 2026-10-20 15:17 – Updated: 2026-11-18 05:33 – Source website
    VLAI
    Summary
    CVE-2026-112909 affecting package python-filelock 3.20.3-4
    Details

    filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. This issue is fixed in version 4.2.1.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: ≤ 3.20.3-4 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "3.20.3-4"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file\u0027s mode. This issue is fixed in version 4.2.1.",
      "id": "AZL-110067",
      "modified": "2026-11-18T05:33:41Z",
      "published": "2026-10-20T15:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112909"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-112909 affecting package python-filelock 3.20.3-4",
      "upstream": [
        "CVE-2026-112909"
      ]
    }

    AZL-74234 (CVE-2026-22701)

    Vulnerability from osv_azurelinux – Published: 2026-01-10 06:15 – Updated: 2026-02-05 20:48 – Source website
    VLAI
    Summary
    CVE-2026-22701 affecting package python-filelock for versions less than 3.20.3-1
    Details

    filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: < 3.20.3-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "3.20.3-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.",
      "id": "AZL-74234",
      "modified": "2026-02-05T20:48:17Z",
      "published": "2026-01-10T06:15:52Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22701"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-22701 affecting package python-filelock for versions less than 3.20.3-1",
      "upstream": [
        "CVE-2026-22701"
      ]
    }

    AZL-79235 (CVE-2026-22701)

    Vulnerability from osv_azurelinux – Published: 2026-01-10 06:15 – Updated: 2026-03-10 17:42 – Source website
    VLAI
    Summary
    CVE-2026-22701 affecting package python-filelock 3.0.12-13
    Details

    filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:2 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: ≤ 3.0.12-13 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:2",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "3.0.12-13"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.",
      "id": "AZL-79235",
      "modified": "2026-03-10T17:42:31Z",
      "published": "2026-01-10T06:15:52Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22701"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-22701 affecting package python-filelock 3.0.12-13",
      "upstream": [
        "CVE-2026-22701"
      ]
    }

    AZL-79232 (CVE-2025-68146)

    Vulnerability from osv_azurelinux – Published: 2025-12-16 19:15 – Updated: 2026-03-10 17:42 – Source website
    VLAI
    Summary
    CVE-2025-68146 affecting package python-filelock 3.0.12-13
    Details

    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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:2 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: ≤ 3.0.12-13 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:2",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "3.0.12-13"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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.",
      "id": "AZL-79232",
      "modified": "2026-03-10T17:42:31Z",
      "published": "2025-12-16T19:15:59Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68146"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2025-68146 affecting package python-filelock 3.0.12-13",
      "upstream": [
        "CVE-2025-68146"
      ]
    }

    AZL-72739 (CVE-2025-68146)

    Vulnerability from osv_azurelinux – Published: 2025-12-16 19:15 – Updated: 2026-01-08 06:23 – Source website
    VLAI
    Summary
    CVE-2025-68146 affecting package python-filelock for versions less than 3.20.1-1
    Details

    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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-filelock
    pkg:rpm/azure-linux/python-filelock
    Affected: < 3.20.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-filelock",
            "purl": "pkg:rpm/azure-linux/python-filelock"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "3.20.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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.",
      "id": "AZL-72739",
      "modified": "2026-01-08T06:23:09Z",
      "published": "2025-12-16T19:15:59Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68146"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2025-68146 affecting package python-filelock for versions less than 3.20.1-1",
      "upstream": [
        "CVE-2025-68146"
      ]
    }