GitPython's Submodule.move() API does not properly handle symbolic links in intermediate path components, allowing an attacker-controlled repository to cause the submodule move operation to escape the intended worktree directory. This can result in moving submodule content outside the parent repository, corrupting the repository's index and configuration state. The vulnerability requires an attacker to control a Git repository with a symlink named 'vendor' pointing outside the worktree and the application to call Submodule.move() with a path under that symlink. No code execution or confidentiality impact has been demonstrated.
CVE-2026-119268 is a use-after-free vulnerability in the Editing component of Google Chrome before version 156.0.8078.79. This flaw allows a remote attacker to execute arbitrary code within the browser's sandbox by crafting a malicious HTML page. The vulnerability has a high severity rating and has been fixed in Chrome version 156.0.8078.79.
CVE-2026-119263 is a use-after-free vulnerability in the GarbageCollection component of Google Chrome prior to version 156.0.8078.79. This flaw allows a remote attacker to execute arbitrary code within the browser's sandbox by crafting a malicious HTML page. The vulnerability has a high severity rating and has been fixed in Chrome version 156.0.8078.79.
An unauthenticated remote denial of service vulnerability exists in the Twisted HTTP/2 server (CVE-2023-44487). A remote client can send a sequence of HTTP/2 frames that cause the server to render requests fully before processing stream resets, allowing CPU exhaustion via rapid stream resets on a single connection. This bypasses the concurrent-stream limit and leads to unbounded request processing. The vulnerability affects Twisted web HTTP/2 server version 26.4.0 and later. There is no impact on confidentiality or integrity, and no code execution is possible.
CVE-2026-112941 is a local integrity vulnerability in filelock's SoftReadWriteLock and AsyncSoftReadWriteLock implementations. A local user with write access to the lock's parent directory can replace the lock directory tree with symbolic links after the lock's initial acquire, causing the lock user process to write lock records through the symlinked paths. This results in the lock user's process deleting or replacing files in directories it can write, such as a private git repository, disrupting its operation. The vulnerability requires specific conditions involving sticky directories or writable parent directories and affects filelock versions 4.1.0 through 4.2.0. The CVSS score is low (3.3) due to local attack vector, low integrity impact, and no confidentiality or availability impact. A fix is available in version 2.19.0_2.
A vulnerability in filelock versions 3.30.0 through 4.2.0 allows a local user with write access to a shared directory to exploit a race condition involving symbolic links in the lock coordination directory. By swapping the .filelock directory with a symbolic link between an lstat check and subsequent operations, the attacker can cause the lock user to create claim files in a directory chosen by the attacker. This can lead to denial of service by causing stranded claims that block other processes from acquiring the lock until manually force-broken.
A symlink swap vulnerability in filelock's SoftFileLock writability check allows a local user to leak one bit of information about whether a path exists and is writable by the lock user. This occurs because the check uses os.lstat followed by os.access, which follows symlinks, enabling a time-of-check to time-of-use (TOCTOU) leak. The vulnerability affects filelock versions 3.32.6 through 4.2.0 and is mitigated on Linux by the fs.protected_symlinks kernel setting in common sticky world-writable directories like /tmp. The impact is limited to leaking a single bit per acquire attempt, with no integrity or availability impact. The vulnerability requires local access, the ability to create entries in the lock directory, and high timing precision to exploit.
Two security vulnerabilities in the pcre2 library for Perl Compatible Regular Expressions have been addressed by Red Hat. These involve out-of-bounds write flaws that could allow arbitrary code execution when processing crafted regular expressions. The issues affect Red Hat Enterprise Linux 8.6 variants and have been rated with an important security impact. Red Hat has released updated packages to fix these vulnerabilities.
The msgpack-python C extension has a memory leak vulnerability triggered when deserialization rejects a map key under strict_map_key validation. This leak causes unbounded memory growth and potential denial of service when processing attacker-controlled MessagePack data. Additionally, the streaming Unpacker API may suffer from use-after-free or double free errors due to stale parser-stack references. The issue affects version 1.2.2 and development commits, with a fix available in version 2.46.7. The pure-Python fallback does not exhibit this leak. Exploitation does not impact confidentiality or integrity but can cause denial of service via resource exhaustion.
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 HTTP redirects and send custom headers and, on certain redirects, the request body to the redirected host. This can expose sensitive headers like API keys to unintended origins if the trusted endpoint redirects to a different host. The SDK now restricts redirects to the same origin or an http-to-https upgrade on the same host. Fixed in versions 1.30.0 and 2.2.0.
Authlib versions including 1.8.0 contain a vulnerability in the OpenID ID token validation process. The parse_id_token() function reads the nonce_supported claim from the ID token payload. If this claim is the boolean false, nonce validation is disabled by setting the expected nonce to None, allowing an attacker to replay a valid signed ID token with a mismatched nonce and authenticate as the victim. This affects implicit and hybrid flows and direct calls to parse_id_token(), but not the authorization code flow. No fixed versions are currently available.