CVE-2026-112910: SQL Injection

filelock on Windows ignores the mode argument. FileLock(path, mode=0o600) creates the same file as FileLock(path): one with no security descriptor of its own (the Windows record that says who may access a file). Its access list, or ACL, is whatever the lock directory hands down to new files. filelock creates the ReadWriteLock database, which it asks to be 0o600, the same way. In a directory whose inheritable ACL grants other local accounts access to new files, those accounts can open the lock file or database. They can take the byte-range lock (a lock on a span of bytes in a file) once the owner releases it and keep the owner's later acquire() calls waiting or timing out. They can read holder metadata an onacquired hook left in a preservelockfile=True file. Where the directory hands down modify access, they can write to both files.

lock.mode still reports 0o600. The documentation neither promises an ACL on Windows nor says that Windows drops the mode. On Unix the same mode keeps other accounts out. Mutual exclusion between processes that follow the protocol holds on either platform. Affected versions are filelock 3.10.0 through 4.2.0 on Windows.

Anthropic's OSS Scanner reported this in private. Finding covered by this advisory:

- ANT-2026-0KEO0DDO [medium, CWE-732]: WindowsFileLock ignores mode; 0o600 lock files inherit the directory ACL.

Severity

CVSS 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L scores 5.3 (Medium).

AV:L (local): the other account needs a logon on the same host. PR:L (low privileges): an ordinary account is enough. UI:N (no user interaction). AC:L (low attack complexity): no race. C:L (partial confidentiality impact): the lock file (holder metadata) and the lock database are readable where 0o600 was meant to keep them private. I:L (partial integrity impact): in the directory layout the maintainers tested, the other account can also write both files, which lets it corrupt the lock's own state but nothing the lock protects. A:L (partial availability impact): the other account can hold the byte-range lock and make the owner wait or time out. S:U (scope unchanged).

Classification from the review: Windows permission failure with security impact only where callers rely on mode=0o600 across accounts. The review had marked it an unconfirmed Windows claim, since the scanner traced stand-in Win32 calls on Linux. The maintainers have since confirmed it on Windows with two local accounts (see Evidence). The scanner rated this medium; the maintainers keep medium.

Scope and preconditions

- The affected classes are FileLock and AsyncFileLock on Windows (WindowsFileLock), and the SQLite database of ReadWriteLock and AsyncReadWriteLock. Both go through opennonreparsefd. The soft locks create their markers with os.open, which also keeps only a read-only bit of the mode on Windows; the scanner did not examine them further. - The directory is one that other local accounts cannot write, which the documentation already requires on Windows, but whose inheritable entries grant them read (or modify) access to new files. Examples are a service's data directory readable by Users, or any directory with (OI)(CI) entries (entries that new files and sub-directories inherit) for another account. A directory whose ACL already excludes other accounts, such as one inside a user profile, hides the problem. - The other account must open the file. According to the LockFileEx documentation, read access is enough to take the byte-range lock, so it can hold the lock whenever the owner does not. The lock file exists while the owner holds the lock, and stays after release with preservelockfile=True. The ReadWriteLock database is not unlinked at any point. - Unix is not affected, because UnixFileLock creates the file with the mode and repeats it with fchmod. Mutual exclusion between cooperating processes is not affected.

Affected code

Scanned commit b831496b0273: opennonreparsefd reduces the mode to one readonly bit. That bit is false for every accepted mode, because checkmode rejects any mode without owner read and write, and an unset mode becomes 0o666. In ntopen the OBJECTATTRIBUTES.SecurityDescriptor field stays unassigned, and readonly only chooses FILEATTRIBUTEREADONLY. openlockdatabase passes 0o600 through the same function on Windows.

Introduced

d0061e4 "added multiuser support and associated tests" (#192, 2023-03-15), first tag 3.10.0 (verified), added the mode parameter and on Windows handed it to os.open, which applies only the read-only attribute. The Windows backend has applied no more of the mode than that at any version, so this is a long-standing gap rather than a regression.

Mechanism

opennonreparsefd(path, mode) computes readonly = not mode & OWNERWRITE and calls ntopen(path, readonly=readonly). ntopen fills an OBJECTATTRIBUTES with the NT path and OBJCASEINSENSITIVE and leaves SecurityDescriptor NULL. It then calls NtCreateFile with FILEOPENIF and FILEATTRIBUTENORMAL (or FILEATTRIBUTEREADONLY when readonly, which no accepted mode produces). Nothing consults the group and other bits. Per the NtCreateFile and OBJECTATTRIBUTES documentation, a NULL descriptor gives the new file default security, which on NTFS is the set of inheritable entries of the parent directory. A lock file created with mode=0o600 in a directory that hands down read access to Users is therefore readable by Users.

Nothing tells the caller. The constructor validates the mode, lock.mode returns 0o600, and hasexplicitmode is True. docs/concepts.rst says "filelock creates the file with it" and that "0o600 and 0o700 keep other UIDs out", with no Windows caveat. Only the opennonreparsefd docstring and a comment in soft.py record the limitation.

Reproduction

The scanner's reproducer for ANT-2026-0KEO0DDO, quoted as received. It ran against commit b831496b0273.

repro

python #!/usr/bin/env python3 import os import shutil import subprocess import sys import tempfile

privatejob = "/tmp/repro.d/jobwithprivatelock.py" # with FileLock(path, mode=0o600) defaultjob = "/tmp/repro.d/jobwithdefaultlock.py" # with FileLock(path) onwindowsbackend = "/tmp/repro.d/runonwindowsbackend.py" # prints every Win32 call filelock makes

os.umask(0o022) locks = tempfile.mkdtemp()

control: UnixFileLock, which leaves the lock file behind subprocess.run([sys.executable, privatejob, f"{locks}/private.lock"], check=True) subprocess.run([sys.executable, defaultjob, f"{locks}/default.lock"], check=True) unixprivatemode = os.stat(f"{locks}/private.lock").stmode & 0o777 unixdefaultmode = os.stat(f"{locks}/default.lock").stmode & 0o777

trigger: the same two programs on WindowsFileLock, same lock name so the call lists can be compared whole windowsprivate = [sys.executable, onwindowsbackend, privatejob, f"{locks}/job.lock"] windowsdefault = [sys.executable, onwindowsbackend, defaultjob, f"{locks}/job.lock"] windowsprivatecalls = subprocess.run(windowsprivate, check=True, captureoutput=True, text=True).stdout.splitlines() windowsdefaultcalls = subprocess.run(windowsdefault, check=True, captureoutput=True, text=True).stdout.splitlines() shutil.rmtree(locks)

check: mode=0o600 must reach the OS; on Windows that means a security descriptor on NtCreateFile print(f"CONTROL UnixFileLock FileLock(path, mode=0o600): lock file mode {unixprivatemode:#o}") print(f"CONTROL UnixFileLock FileLock(path): lock file mode {unixdefaultmode:#o}") for call in windowsprivatecalls: print(f"OBSERVED WindowsFileLock FileLock(path, mode=0o600): {call}") for call in windowsdefaultcalls: print(f"OBSERVED WindowsFileLock FileLock(path): {call}") print(f"OBSERVED the two Win32 call lists are identical: {windowsprivatecalls == windowsdefaultcalls}")

honouredonunix = unixprivatemode == 0o600 and unixdefaultmode == 0o644 privatecreate = next(call for call in windowsprivatecalls if call.startswith("NtCreateFile(")) droppedonwindows = ( "ObjectAttributes.SecurityDescriptor=None" in privatecreate and windowsprivatecalls == windowsdefaultcalls ) print("BUG" if honouredonunix and droppedonwindows else "OK")

repro.d/jobwithdefaultlock.py

python import sys

from filelock import FileLock

with FileLock(sys.argv[1]): pass

repro.d/jobwithprivatelock.py

python import sys

from filelock import FileLock

with FileLock(sys.argv[1], mode=0o600): pass

repro.d/runonwindowsbackend.py

python import ctypes import fcntl import os import runpy import sys import types

Stand-ins for the ntdll, kernel32 and msvcrt functions filelock's Windows backend calls. Each prints the call with the arguments filelock passed, then does the nearest Linux thing so the program runs to its end.

def RtlDosPathNameToNtPathNameUWithStatus(dospath, ntname, filepart, relativename): print(f"RtlDosPathNameToNtPathNameUWithStatus({os.path.basename(dospath)!r})") ntname.obj.Buffer = os.path.abspath(dospath) return 0 # STATUSSUCCESS

def NtCreateFile( handle, access, attributes, iostatus, allocationsize, fileattributes, share, disposition, options, ea, ealength ): objectattributes = attributes.obj print( f"NtCreateFile(DesiredAccess={access:#x}," f" ObjectAttributes.Attributes={objectattributes.Attributes:#x}," f" ObjectAttributes.SecurityDescriptor={objectattributes.SecurityDescriptor}," f" AllocationSize={allocationsize}, FileAttributes={fileattributes:#x}, ShareAccess={share:#x}," f" CreateDisposition={disposition}, CreateOptions={options:#x}, EaBuffer={ea}, EaLength={ealength})" ) path = objectattributes.ObjectName.contents.Buffer handle.obj.value = os.open(path, os.ORDWR | os.OCREAT | os.ONOFOLLOW) return 0 # STATUSSUCCESS

def RtlFreeUnicodeString(ntname): print("RtlFreeUnicodeString()")

def GetFileInformationByHandle(handle, info): print("GetFileInformationByHandle()") info.obj.dwFileAttributes = 0x80 # FILEATTRIBUTENORMAL: not a reparse point return True

def LockFileEx(handle, flags, reserved, byteslow, byteshigh, overlapped): print(f"LockFileEx(dwFlags={flags:#x}, nNumberOfBytesToLockLow={byteslow}, nNumberOfBytesToLockHigh={byteshigh})") fcntl.flock(handle, fcntl.LOCKEX) return True

def UnlockFileEx(handle, reserved, byteslow, byteshigh, overlapped): print(f"UnlockFileEx(nNumberOfBytesToUnlockLow={byteslow}, nNumberOfBytesToUnlockHigh={byteshigh})") fcntl.flock(handle, fcntl.LOCKUN) return True

only a filelock that builds a security descriptor for the lock file calls this def ConvertStringSecurityDescriptorToSecurityDescriptorW(sddl, revision, descriptor, size): print(f"ConvertStringSecurityDescriptorToSecurityDescriptorW({sddl!r})") descriptor.obj.value = 1 # any address but NULL return True

filelock sets argtypes on these at import; a lock taken without contention never calls them def notcalled(arguments): raise NotImplementedError

dlls = { "ntdll": types.SimpleNamespace( RtlDosPathNameToNtPathNameUWithStatus=RtlDosPathNameToNtPathNameUWithStatus, NtCreateFile=NtCreateFile, RtlFreeUnicodeString=RtlFreeUnicodeString, RtlNtStatusToDosError=notcalled, ), "kernel32": types.SimpleNamespace( GetFileInformationByHandle=GetFileInformationByHandle, LockFileEx=LockFileEx, UnlockFileEx=UnlockFileEx, CloseHandle=notcalled, OpenProcess=notcalled, GetProcessTimes=notcalled, ), "advapi32": types.SimpleNamespace( ConvertStringSecurityDescriptorToSecurityDescriptorW=ConvertStringSecurityDescriptorToSecurityDescriptorW, ), }

Import filelock once on the real platform, so the standard library modules it uses load their Linux versions, then drop it and import it again with the Windows branches active. A HANDLE is the Linux descriptor number. import filelock # noqa: E402

for name in [name for name in sys.modules if name.split(".")[0] == "filelock"]: del sys.modules[name]

ctypes.WinDLL = lambda name, uselasterror=False: dlls[name] sys.modules["msvcrt"] = types.SimpleNamespace(openosfhandle=lambda handle, flags: handle, getosfhandle=lambda fd: fd) os.ONOINHERIT = 0 sys.platform = "win32"

import filelock # noqa: E402, F811

assert filelock.FileLock is filelock.WindowsFileLock

sys.argv = sys.argv[1:] runpy.runpath(sys.argv[0], runname="main")

Failure sequence

mermaid sequenceDiagram participant O as owner process: FileLock(path, mode=0o600) participant N as NtCreateFile participant F as lock file (inherits the directory ACL) participant U as other local account O->>N: opennonreparsefd(path, 0o600): readonly=False, SecurityDescriptor=NULL rect rgb(255, 214, 214) N-->>F: created with the parent's inheritable entries only, group and other bits not consulted Note over F: the file reports mode 0o600 to the owner, the ACL says otherwise end O->>F: LockFileEx (holds the lock), release, unlock U->>F: open for read (and write, where the directory hands down modify) U->>F: LockFileEx through that handle O->>F: acquire() -> waits or Timeout while U holds the byte-range lock U->>F: read holder metadata left by onacquired with preservelockfile=True

Evidence

The scanner's reproducer runs on a Linux image. It imports filelock's unmodified Windows backend with sys.platform == "win32" over stand-ins that print every Win32 call. The program with mode=0o600 and the one without produce identical call lists (RtlDosPathNameToNtPathNameUWithStatus, NtCreateFile with FileAttributes=0x80 and ObjectAttributes.SecurityDescriptor=None, RtlFreeUnicodeString, GetFileInformationByHandle, LockFileEx, UnlockFileEx), while the Unix control produced 0o600 and 0o644 files. It prints OBSERVED the two Win32 call lists are identical: True and BUG. The scanner stated that it inferred the resulting ACL, and what another user can then do, from the documentation and did not run on Windows.

Maintainer triage: the stand-in reproducer prints BUG on the scanned commit b831496 and on the 4.2.0 release image.

Maintainer verification on Windows 11 with two local accounts: a script creates private.lock with FileLock(mode=0o600, preservelockfile=True), default.lock without a mode, and a ReadWriteLock database lock.db as the first account, in a directory granted (OI)(CI)(M) to a second account that is a member of Users. It then opens each file under the second account's logon token with LogonUserW and ImpersonateLoggedOnUser. On 4.2.0 the second account could open private.lock and lock.db for both read and write, the same as default.lock, and icacls listed only inherited (I) entries on all three. This confirms the claim the review had marked unconfirmed.

Impact

A program that passes mode=0o600 so that other accounts cannot open its lock file gets no such restriction on Windows. In a directory that hands down read access, another account can hold the lock and make the owner wait or time out, and read holder metadata in a preserved lock file. Where the directory hands down modify access, as in the maintainers' test, it can also write the lock file and the ReadWriteLock database. With the mode honoured, as on Unix, a user without write access to the directory can do none of this. The exposure ends there: the effect reaches only the lock file or lock database, and mutual exclusion between processes that follow the protocol still holds.

Workarounds

- On Windows, keep lock files and ReadWriteLock databases in a directory whose ACL already excludes other accounts (inside the user profile, or a directory with inheritance disabled and only the owner, SYSTEM and Administrators granted), rather than relying on mode. - After creating a lock file with preservelockfile=True or a ReadWriteLock database, set its ACL yourself, for example icacls <file> /inheritance:r /grant:r "<owner>:F" "SYSTEM:F" "Administrators:F"; a file that exists keeps its ACL on later opens. - Do not store anything confidential in the lock file through onacquired on Windows.

Patched version

4.2.1.

Fix: https://github.com/tox-dev/filelock/pull/835

Credits

Reported by Anthropic's OSS Scanner (automated analysis), 15 October 2026; reviewed by the maintainers.

- 2026-10-15 23:08 UTC: report received (36 findings; this one rated medium by the scanner) - 2026-10-16 05:38 UTC: draft advisory created (first as part of GHSA-69hj-f68j-2879, then split out); two-account verification on Windows by the maintainers - 2026-10-16 01:16 UTC: fix PR #835 opened