CVE-2026-112941 is a low-severity local vulnerability in filelock versions >=4.1.0 and <=4.2.0 involving SoftReadWriteLock. It allows a local user with write access to the lock's parent directory to replace the lock directory tree with symbolic links after the first lock acquire, causing the lock user's process to write lock records into attacker-controlled paths. This results in integrity impact by replacing or deleting files in directories writable by the lock user, such as breaking a git repository's HEAD file. There is no confidentiality or availability impact. The vulnerability requires the attacker to have local access and write permissions to the lock's parent directory, with additional conditions depending on sticky bit settings. A fix is available in version 1.79.0_1.
A vulnerability in filelock versions 3.30.0 through 4.2.0 allows a local user with write access to rename the lock coordination directory (<path>.filelock) to a symbolic link after an initial check, causing the lock user to create claim files in an attacker-chosen directory. This can cause denial of service by making another strict lock time out until manually force-broken. The issue requires a race condition and specific directory permissions to exploit.
A vulnerability in filelock versions 4.1.0 through 4.2.0 allows a local unprivileged user who can write to a shared lock directory without the sticky bit to exploit a race condition in the SoftFileLock stale-break restore process. This leads to the creation of a hard link to a file owned by the lock user, exposing file metadata and enabling the attacker to manipulate the file via the new link. The issue arises due to symbolic link following behavior in CPython 3.12+ on Linux and macOS during the restore operation.
A symlink swap vulnerability in the SoftFileLock implementation of the filelock library (versions 3.32.6 through 4.2.0) allows a local user with write access to the lock directory to leak one bit of information about whether a path exists and is writable by the lock user. This occurs due to a time-of-check to time-of-use (TOCTOU) race condition in the writability check that follows symlinks under certain conditions. The vulnerability is mitigated on Linux by the fs.protected_symlinks kernel setting in sticky world-writable directories like /tmp, but not in other directory permission configurations. The impact is limited to a low-severity confidentiality leak of one bit per lock acquire attempt, with no integrity or availability impact. A fix is available in filelock version 1.79.0_1.
The SoftReadWriteLock mechanism in filelock versions 4.0.0 through 4.2.0 refreshes its holder record by reopening and writing to a file without verifying the file type beyond symbolic links. This allows a local user who owns the lock's .rw directory tree to rename a FIFO (named pipe) or a hard link over the holder record file, causing the lock user's write operation to hang or overwrite private files. The FIFO variant causes the lock user's heartbeat thread to hang indefinitely, allowing multiple processes to believe they hold the lock simultaneously. The hard link variant can overwrite the first ~135 bytes of a private file if the kernel permits hard links to files not owned by the user. The vulnerability requires local access and ownership of the lock directory tree and is rated medium severity with a CVSS score of 6.1. A fix is available in filelock version 1.56.0_1.
The Model Context Protocol (MCP) Python SDK versions 1.8.0 through 1.29.1 and 2.0.0 through 2.1.1 have a vulnerability where their HTTP client transports follow cross-origin redirects and send custom headers and request bodies to the redirected host. This can expose sensitive headers like X-API-Key if an attacker can cause a trusted endpoint to redirect to a malicious or unintended host. The OAuth client providers in the SDK exhibit the same behavior. The lone Authorization bearer header is not exposed due to existing HTTP library protections. The issue is fixed in MCP SDK versions 1.30.0 and 2.2.0 or later.
GitPython's Submodule.move() API does not properly validate intermediate symbolic links in the destination path, allowing an attacker-controlled symlink to redirect the move operation outside the intended repository worktree. This can cause the submodule checkout to be moved to an attacker-selected directory outside the parent repository, corrupting the repository's index and configuration state. The vulnerability requires an attacker-controlled Git repository with a symlink and an application that calls Submodule.move() with a fixed path under that symlink. No code execution or confidentiality impact is demonstrated.
The msgpack-python C extension has an unbounded memory leak triggered when deserialization rejects a map key under strict_map_key validation. This leak occurs because the decoded map value is not released on error, causing process memory growth and potential denial of service. Additionally, the streaming Unpacker API may suffer from a use-after-free or double decrement issue due to stale parser-stack references. The pure-Python fallback does not exhibit this leak. The issue affects msgpack-python version 1.2.2 and development commits, with a fix available in version 13.8.0_3 of the affected product.