A security update for Mozilla Firefox Extended Support Release 153.6.0 ESR addresses multiple vulnerabilities including privilege escalations, remote code execution, sandbox escapes, information disclosure, use-after-free, and incorrect boundary conditions across various components such as DLL Services, Brotli decoder, DOM, Networking, Audio/Video, JavaScript engine, Graphics, and Layout. These vulnerabilities collectively pose significant security risks if exploited.
A vulnerability was determined in kongxin-github Java_Library_Management_System up to 70a6eb6b96fe64575d8051f1a59055bfc5dc5885. This affects the function UpdateAdmin.deleteuser/UpdateAdmin.updateadmin/UpdateAdmin.updatepass/Book.addbook/Book.modifybook/Book.deletebook/Category.addcategory/Category.setcategory/Landing.sureadmin of the file src/view/MainInterface.java of the component Swing UI Layer. This manipulation causes improper authorization. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-124590 is an improper authorization vulnerability in the zhangbw409 library_manager_system affecting the BookController.addBook function. The flaw involves manipulation of user-related arguments (userName, userPwd, userEmail, userId) that can lead to unauthorized actions. The vulnerability can be exploited remotely and public exploit details have been disclosed. The product uses a rolling release model, so no specific affected versions are identified. The vendor has not yet responded to the issue report.
CVE-2026-112941 describes a local integrity vulnerability in the SoftReadWriteLock implementation used by filelock versions 4.1.0 through 4.2.0. A local unprivileged user with write access to the lock's parent directory can replace the lock directory tree with symbolic links after the lock's initial acquisition, causing the lock user process to write lock records into attacker-controlled paths. This results in the lock user's files being replaced or deleted, breaking functionality such as a git repository's operation. The vulnerability requires specific conditions including directory write access and the presence of sticky bits in parent directories like /tmp. The impact is limited to integrity loss with no confidentiality or availability impact. The CVSS 3.1 base score is 3.3 (Low).
A vulnerability in filelock versions 3.30.0 through 4.2.0 allows a local user with write access to a shared directory to swap a symbolic link in place of a lock coordination directory during a critical timing window. This causes the lock user's process to create claim files in a directory chosen by the attacker but writable only by the lock user. The impact includes denial of service by causing stranded claims that block other locks until manually force-broken. The vulnerability requires local access and specific directory permissions, with medium severity (CVSS 5.8).
A vulnerability in filelock versions 4.1.0 through 4.2.0 allows a local unprivileged user to exploit a race condition in the SoftFileLock stale-break restore process. By replacing a lock file marker with a symbolic link in a writable, non-sticky shared directory, the attacker can cause the lock user to create a hard link to one of their own files. This exposes file metadata and allows the attacker to manipulate the file's name. On version 4.2.0, this can lead to truncation of the file by the lock user's subsequent FileLock operation. The vulnerability requires specific conditions including a writable non-sticky directory and CPython 3.12 or later on Linux/macOS.
A symlink swap race condition in the SoftFileLock implementation of the filelock library allows a local user with write access to the lock directory to leak one bit of information about the existence and writability of arbitrary paths. This occurs because the writability check follows symlinks under certain conditions, revealing whether the symlink target exists and is writable by the lock user. The issue 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 vulnerability has low severity due to high attack complexity and limited information leakage.
A security update for webkit2gtk3 addresses multiple vulnerabilities in the Skia graphics library used by chromium-browser within WebKitGTK. These include information leaks, use-after-free, cross-origin data disclosure, uninitialized resource usage, integer overflow, out-of-bounds reads, memory corruption, and improper input validation. The update is rated as important by Red Hat and affects Red Hat Enterprise Linux 8 variants. The advisory references numerous CVEs detailing these issues.
Red Hat OpenShift Container Platform 4.19.55 includes critical security updates addressing two vulnerabilities: CVE-2026-98432, a kernel IPv4 issue involving freeing inet_opt and ireq_opt after an RCU grace period, and CVE-2026-111497, an out-of-bounds write vulnerability in the Google Brotli decoder. Users of OpenShift Container Platform 4.19 are advised to upgrade to this release to mitigate these issues. Detailed upgrade instructions and release notes are provided by Red Hat.
A security update for webkit2gtk3 addresses multiple vulnerabilities in the Skia graphics library used by chromium-browser, including information leaks, use-after-free, cross-origin data disclosure, integer overflow, out-of-bounds reads, memory corruption, and improper input validation. These issues could lead to information disclosure and memory corruption. The vulnerabilities affect versions of webkit2gtk3 prior to 2.54.2-2.el8_10. A patch is available and has been released in version 2.54.2-2.el8_10.
Multiple vulnerabilities have been identified in the JetBrains Toolbox App, a tool used for managing, updating, and launching JetBrains development environments and tools. These vulnerabilities affect versions prior to and including 3.6.1. A fix for these issues is available in version 3.6.1.
Brava Security is a cybersecurity startup that has emerged from stealth mode with $15 million in funding. The company offers an AI-powered platform that simulates attacker behavior to generate telemetry resembling real attacks, helping organizations identify gaps in their security defenses. The platform integrates with existing security infrastructure without requiring changes and provides insights quickly after onboarding. This solution aims to improve detection capabilities by modeling how attacks would appear in specific environments, thereby enhancing the effectiveness of security monitoring tools.
Zebra versions from 2.3.0 up to but not including 7.0.0 have a denial of service vulnerability. This flaw allows unauthenticated peers to bypass misbehavior scoring by submitting transactions or blocks containing invalid transparent scripts. Exploitation can lead to mempool flooding with script-failing transactions or delivery of forged v5 block bodies with altered scriptSig bytes, causing CPU exhaustion and repeated stalling of block synchronization.
ZcashFoundation Zebra zebrad versions before 7.0.0 have a reachable assertion race condition that allows unauthenticated remote peers to abort the node. This occurs when malicious peers trigger disconnection during a blocked outbound send by returning empty FindBlocks or FindHeaders replies and ceasing to read their socket, causing syncing nodes to terminate.
Rust rustls versions before 0.23.46 have an uncontrolled memory allocation vulnerability in the optional Brotli certificate decompression feature. The flaw arises because the decompression accepts a large history window size from input, which can request up to 1 GiB of memory allocation before authentication. This can cause clients or servers using Brotli-enabled rustls to abort if their allocator cannot satisfy the large memory request. The vulnerability has a low severity rating and does not impact confidentiality or integrity.
Rust Hickory DNS libraries hickory-proto versions 0.25.0-alpha.3 through 0.25.2 and hickory-net versions before 0.26.1 contain an unbounded loop vulnerability in the NSEC3 closest-encloser proof validation. This occurs when the SOA owner is not an ancestor of the queried domain name (QNAME). An attacker can exploit this by returning NoData or NXDomain responses with a cross-zone SOA record, causing panic in debug builds or memory exhaustion in release builds.