CVE-2026-112915

The filelock Python library (versions 3.20.4 through 4.2.0 ) is vulnerable to a Denial of Service (DoS) via CWE-400 in its ReadWriteLock component. A local user capable of replacing the lock database can provide a crafted SQLite database that lacks bounded schema and query work limits. This cause...

PT-2026-118399

Name of the Vulnerable Software and Affected Versions filelock versions 4.1.0 through 4.2.0 Description The ReadWriteLock function can remove a randomized .filelock- private-hard-link directory during cleanup. This allows a local user with rename access in a non-sticky parent directory to observe...

PT-2026-118401

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.2.0 Description The ReadWriteLock allows SQLite to reopen the database and side files by name. On POSIX systems, an attacker with rename access in a non-sticky parent directory can swap these names to trigger...

PT-2026-118395

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.2.0 Description The ReadWriteLock component can open a specially crafted SQLite lock database without bounding schema and query work. This allows a local user who can replace the database to cause the...

PT-2026-118398

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.0.8 Description The ReadWriteLock and AsyncReadWriteLock functions resolve the lock path and pass it to SQLite without rejecting a final symbolic link. This allows a local user with permissions to create name...

tox-dev filelock: race condition issue

The tox-dev filelock version 4.1.0 to 4.2.1 prior to version 4.2.1 has a race condition vulnerability. This vulnerability arises due to race conditions during cleanup by the ReadWriteLock. It allows other local users with rename permissions in non-sticky parent directories to observe activity nam...

tox-dev filelock: race condition issue

The tox-dev filelock version 3.20.4 up to version 4.2.1 has a race condition vulnerability. This vulnerability stems from the ReadWriteLock mechanism, which allows SQLite to reopen databases and associated files by their names. Attackers with renaming privileges on POSIX systems can replace these...

tox-dev filelock backend link vulnerability

The tox-dev filelock version 3.20.4 to 4.0.9 contains security vulnerabilities. These vulnerabilities stem from the way ReadWriteLock and AsyncReadWriteLock handle lock paths, which allow them to pass the final symbolic link to SQLite without being rejected. This may lead to other local users...

tox-dev-filelock Resource Management Error Vulnerability

The tox-dev filelock version 3.20.4 to 4.2.1 contained a resource management vulnerability. This vulnerability stemmed from the ReadWriteLock being used to open custom SQLite lock databases without limiting the workload on schemas and queries. As a result, local users who had access to the databa...

AZL-91287 CVE-2026-54906 affecting package rubygem-concurrent-ruby for versions less than 1.3.7-1

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLockreleasewritelock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can...

CVE-2026-54906

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLockreleasewritelock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can...

EUVD-2026-38811

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLockreleasewritelock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can...

CVE-2026-54906: Missing Lock Check

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLockreleasewritelock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can...

This Week in Spring - July 16th, 2024

Hi, Spring fans! Welcome to another installment of This Week in Spring! It's the middle of July! I can't believe it! Things have been just rushing by! did you see this awesome talk on observability by Tommy Ludwig and Jonatan Ivanov from Spring IO 2024? What is a ReadWriteLock? Spring for GraphQL...