A race condition vulnerability (CWE-363) exists in tox-dev's filelock Python package versions from 3.20.4 up to but not including 4.2.1. This flaw allows an attacker with rename access on POSIX systems to swap file names in a non-sticky parent directory, potentially causing overwrite or unlink operations on SQLite database files. Exploitation requires a writable adjacent hot journal file to overwrite content with attacker-chosen data. The issue is fixed in version 4.2.1.
filelock, a Python platform-independent file lock library used by tox-dev, has a race condition vulnerability in versions 4.1.0 through 4.2.0. This flaw allows a local user with rename permissions in a non-sticky lock directory to exploit SoftFileLock's stale marker restoration by swapping in a symbolic link. If the runtime follows the link and the target is on the same filesystem, the attacker can cause the lock user to hard-link one of its files into the lock directory. The issue is resolved in version 4.2.1.
CVE-2026-91203 is a race condition vulnerability in cockpit-files on Red Hat Enterprise Linux 10. It allows a local attacker to exploit a symlink race during privileged file operations, such as changing file ownership or permissions. By winning this timing race, the attacker can redirect these operations to arbitrary files, potentially causing unauthorized changes to file ownership and permissions. This may compromise system integrity and availability by altering system or application states or making services unusable.
A race condition vulnerability exists in the cockpit-files package on Red Hat Enterprise Linux 9 and related distributions. A local unprivileged attacker with write access to a parent directory can replace a newly created directory with a symbolic link before the ownership change is applied, redirecting ownership changes to arbitrary files. This can lead to information disclosure or unauthorized modification of sensitive files such as /etc/shadow. Exploitation requires local access, an attacker-writable parent directory, user interaction, and winning a narrow race window. A fix is being developed for actively maintained releases, while some deferred streams will not receive immediate fixes due to moderate severity and exploitation difficulty. Mitigations include avoiding privileged owner-assignment directory creation in writable directories by untrusted users and applying the sticky bit on shared writable directories.
On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem without permitting reading or writing files outside the root.
A potential security vulnerability has been identified in HP Image Assistant for versions prior to 5.3.3. The vulnerability
could potentially allow a local attacker to escalate privileges via a race condition when installing packages.
runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7, 1.3.2 and 1.4.0-rc.2, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
runc is a CLI tool for spawning and running containers according to the OCI specification. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.
CVE-2025-31133 is a vulnerability in the runc container runtime tool where insufficient verification of the source of bind-mounts for /dev/null allows attackers to exploit symbolic link following. This flaw enables arbitrary mount gadget attacks that can lead to host information disclosure, denial of service, container escape, or bypassing of maskedPaths protections. The issue affects specific versions of runc prior to 1.2.8, between 1.3.0-rc.1 and before 1.3.3, and certain 1.4.0 release candidates. It has a high severity rating and a CVSS 4.0 score of 7.3. Fixes are available in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
Youki is a container runtime written in Rust. In versions 0.5.6 and below, youki’s apparmor handling performs insufficiently strict write-target validation, and when combined with path substitution during pathname resolution, can allow writes to unintended procfs locations. While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target. This issue is fixed in version 0.5.7.
Youki is a container runtime written in Rust. In versions 0.5.6 and below, the initial validation of the source /dev/null is insufficient, allowing container escape when youki utilizes bind mounting the container's /dev/null as a file mask. This issue is fixed in version 0.5.7.