The Wild Apricot Login plugin for WordPress versions up to 1.0.18 contains an authentication bypass vulnerability via SSO email-collision account binding. Attackers controlling a Wild Apricot contact with an email matching a WordPress administrator can authenticate as that administrator without proof of account ownership. This allows issuance of a valid network-wide authentication cookie on WordPress Multisite networks, granting administrator access across subsites.
A vulnerability in mem0ai's session key construction allows cross-tenant data leakage and corruption. The function _build_session_scope() concatenates user_id, agent_id, and run_id with unescaped '&' and '=' delimiters, enabling an attacker controlling only run_id or agent_id to craft values that collide with another tenant's session key. This leads to unauthorized reading and overwriting of another tenant's conversation history. The flaw affects both Python and TypeScript SDKs and is fixed in versions 2.0.18 and 3.1.6.
CVE-2026-118688 is a vulnerability in wasmtime-wasi in Wasmtime versions before 36.0.18, 48.0.6, and 49.0.3. It involves the re-appending of a trailing slash to rename source paths, which causes the renameat system call on macOS and FreeBSD hosts to follow directory symbolic links (symlinks). This allows a guest with sandbox write access to rename a relative symlink such as "up/" to move host directories into its sandbox, potentially enabling unauthorized read or write access to host directories.
Red Hat has released a security advisory for a kernel live patch module targeting kernel-4.18.0-477.107.1.el8_8. The update addresses multiple vulnerabilities including issues in netfilter ebtables SNAT target, pppoe header pointer handling, bridge fast-leave behavior, packet hard_header_len consistency, and xfrm ah6 routing header validation. These vulnerabilities have been assigned CVE identifiers CVE-2026-53266, CVE-2026-68121, CVE-2026-74480, CVE-2026-74582, and CVE-2026-80844 respectively. The advisory rates the update as important and provides fixes via kpatch live patch modules for Red Hat Enterprise Linux 8.8 variants.
CVE-2026-99178 is a vulnerability in the Linux kernel's x86 KVM subsystem involving improper handling of asynchronous page fault (async #PF) flags during nested page faults in non-maskable interrupt (NMI) context. This flaw can cause a kernel panic when an async page fault is consumed incorrectly in NMI context, leading to system instability. The issue was resolved by ensuring the async #PF flags are not consumed on a kernel page fault in NMI context, preserving the flags for the interrupted handler. The fix is included in Linux kernel versions 6.18.59 and 7.2.13 and later.
CVE-2026-110879 is a critical deserialization vulnerability in FasterXML jackson-databind affecting versions from 2.10.0 up to but not including fixed releases 2.18.12, 2.21.8, 2.22.4, 3.1.8, and 3.2.4. The flaw allows attacker-controlled classes inside generic type arguments to bypass validation, enabling deserialization of malicious payloads. This can lead to arbitrary code execution, notably when combined with Spring on the classpath and attacker-controlled XML input.
The private keys of eight eMudhra intermediate CA certificates were compromised and subsequently revoked on October 18, 2026. This incident affects NetApp ONTAP 9 products that rely on these certificates. Although this is not a traditional software vulnerability, it has been assigned CVE-2026-22063 to track the impact on NetApp products. A fixed version, 9.18.1, addresses the issue by presumably removing or replacing the affected certificates.
MLflow's CrewAI autologging feature in versions >=2.19.0 and <3.17.0 leaks CrewAI LLM provider API keys in trace telemetry. The vulnerability arises because MLflow serializes the CrewAI Agent object's __dict__ including the LLM object, whose string representation contains the API key in plaintext. This sensitive information is unintentionally sent to MLflow's trace backend or any configured OTLP destination without explicit logging by the application. The issue affects MLflow 3.16.0 with CrewAI 1.15.18 and is fixed in MLflow 3.17.0.
CVE-2026-113723 is a vulnerability in virtualenv's bash activation prompt handling where attacker-controlled prompt text can be interpreted as executable shell syntax under certain older bash compatibility modes (4.2 and lower) or when using dash shell. This can lead to command execution when the environment is activated and the prompt is drawn. The issue arises because the prompt string assigned to PS1 is expanded twice by the shell, and some code paths do not properly escape or sanitize the prompt text. The vulnerability affects virtualenv versions from 1.2.0 up to but not including 1.6.2 and 1.9.3 up to but not including 1.18.1_2. A fix is available in versions 1.6.2 and 1.18.1_2.
Virtualenv versions prior to 1.6.2 and 1.18.1_2 have a file permission issue where files copied from a cached app-data directory retain their original permissions, potentially allowing wider access than intended. This occurs because shutil.copy preserves cached file modes regardless of the current umask, leading to files with overly permissive modes in new environments. An attacker with access to the new environment and the ability to traverse it can exploit this to modify files such as pip/__init__.py, which then run with the environment owner's privileges.
CVE-2026-113719 is a vulnerability in virtualenv's app-data seeder where the removal of previously installed seed packages does not properly validate deletion paths. This allows deletion of files outside the intended environment if malicious distribution metadata is present. The flaw occurs during environment creation when reusing an existing environment containing manipulated package metadata. The issue was introduced in version 20.8.1 and fixed in versions 1.6.2 and 1.18.1_2 of the affected product. Exploitation requires attacker-controlled metadata and deletion rights by the invoking user. The CVSS score is 4.5 (medium severity).
A vulnerability in filelock's ReadWriteLock and AsyncReadWriteLock components allows a local user with write permissions in the directory containing the lock database to exploit SQLite's behavior of reopening lock files by name, following symlinks and acting on side files like -journal, -wal, and -shm. This can lead to the attacker writing arbitrary data into the lock user's files, creating or unlinking files, or causing lock acquisition failures. The issue affects filelock versions 3.20.4 through 4.2.0, with fixes available in version 1.18.1_2. The vulnerability requires specific directory permissions (non-sticky, writable by the attacker) and local access. It has a CVSS 3.1 score of 7.1 (High) with no confidentiality impact but high integrity and availability impacts.
A vulnerability in filelock versions 4.1.0 through 4.2.0 allows a local unprivileged user to exploit a race condition in the soft-lock stale break restore process. This occurs when the user can write to a shared lock directory without the sticky bit, replacing a lock file marker with a symbolic link. The lock user's process then creates a hard link to one of its own files via the symbolic link, exposing file metadata and allowing the other user to manipulate the file's name. On version 4.2.0, this can lead to truncation of the lock user's file. The vulnerability requires specific conditions including a writable non-sticky directory and CPython 3.12 or later on Linux or macOS. The CVSS 3.1 score is 5.3 (Medium). A fix is available in version 1.18.4 for the related product pipx.
A critical Cross-Site Request Forgery (CSRF) vulnerability exists in Tribulant Software Newsletters newsletters-lite versions up to 4.18.2. This flaw allows an attacker to perform unauthorized actions on behalf of an authenticated user by exploiting the lack of proper request validation.
CVE-2026-108303 is a high-severity vulnerability in Tanium Certificate Manager that allows unauthorized code execution due to improper neutralization of special elements in commands, commonly known as command injection. The flaw affects versions 1.17 up to but not including 1.17.417, 1.18 up to but not including 1.18.368, and 1.22 up to but not including 1.22.119. Tanium has released fixed versions to address this issue.