Trending now

CVE-2026-114820 is a security vulnerability affecting Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition, specifically within the Java Secure Socket Extension (JSSE) component. The issue is tied to a certificate trust compromise involving the private keys of eight intermediate Certificate Authority (CA) certificates issued by eMudhra. In response, Oracle released updates to remove the affected root CA certificates—such as emSign Root CA and AAA Certificate Services—from the Java trust store to prevent unauthorized trust decisions. An unauthenticated attacker with network access can exploit this vulnerability across multiple protocols without requiring user interaction. By intercepting network traffic, an attacker can impersonate trusted websites and services, enabling them to read, modify, or delete data accessible to the affected Java runtime. The vulnerability also applies to client-side Java deployments, such as sandboxed Java Web Start applications or applets that load untrusted code. Remediation involves updating the Java runtime to a patched version or manually removing the compromised root certificates from the system's keystore.

CVE-2026-98432 is a use-after-free vulnerability in the Linux kernel's IPv4 TCP handshake path, affecting kernels dating back to version 4.4. The flaw stems from a race condition involving the ownership and reclamation of IPv4 option data (such as Timestamp or Record Route options) associated with a TCP request socket. When a connection progresses, two processors can act on related request and child sockets while referencing the same IP options object. This allows one path to free the object while another continues to use it, resulting in a stale kernel pointer that can be reached through network traffic. The vulnerability gained significant attention after Anthropic demonstrated that its AI model, Claude, could generate a proof-of-concept exploit for it. The exploit targets Linux servers running a multipath TCP (MPTCP) listener, allowing a remote, unauthenticated attacker to execute arbitrary commands as root. It achieves this in two stages: first, by exploiting the race condition to leak a kernel pointer and bypass Kernel Address Space Layout Randomization (KASLR), and second, by triggering the use-after-free to overflow a buffer and overwrite a callback pointer with a staged payload. The vulnerability has since been patched upstream and backported to all maintained stable kernel branches.

CVE-2026-109618 is a remote code execution (RCE) vulnerability affecting the PHP core. The flaw reportedly impacts a wide range of PHP versions, specifically versions 5, 6, 7, and 8. While specific technical details have been withheld by researchers to prevent exploitation, cybersecurity firm watchTowr confirmed the vulnerability's validity and successfully reproduced it in their testing environment. The vulnerability was originally under embargo for a coordinated disclosure on October 22, 2026, but details of the flaw leaked early on October 20, 2026, via a post on Hacker News. In response to the premature leak, the PHP security team accelerated its release timeline, scheduling emergency security updates for October 21, 2026, to address the issue.

CVE-2026-109619 is a remote code execution (RCE) vulnerability affecting the PHP scripting language. Security researchers and early reports indicate that the flaw impacts PHP versions 5, 6, 7, and 8. While specific technical details regarding the vulnerability's mechanics have not been publicly disclosed, successful exploitation could allow an unauthenticated remote attacker to execute arbitrary code with the privileges of the underlying PHP process. The vulnerability was originally scheduled for coordinated disclosure under embargo on October 22, 2026. However, after information about the flaw leaked online on October 20, the PHP security team accelerated its timeline, scheduling a security release for October 21, 2026, at 14:00 UTC. Security organizations and researchers have advised administrators to prepare to apply the upcoming patches as soon as they are released.

CVE-2026-111357 is a privilege escalation vulnerability affecting Ivanti Connect Secure VPN appliances. The flaw stems from the system mishandling how the privileged `dsinvoked` broker trusts configuration data stored in the `DSCache`. By manipulating this trust—specifically by temporarily modifying library code in memory and altering a maintenance task in the configuration store—an attacker with local authenticated access can execute arbitrary code with root-level privileges. Discovered by cybersecurity firm Volexity, this vulnerability was actively exploited in the wild in October 2026 by a threat actor tracked as UTA0576. The attacker chained CVE-2026-111357 with an authentication bypass (CVE-2026-104935) and a predictable-filename weakness (CVE-2026-118527) to achieve unauthenticated root access on fully patched appliances, which they used to harvest Active Directory credentials and sensitive metadata. In response, Ivanti released security patches on October 29, 2026, and the Cybersecurity and Infrastructure Security Agency (CISA) added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog.

CVE-2026-118527 is a vulnerability in Ivanti Connect Secure (ICS) VPN appliances involving the generation of predictable numbers or identifiers, specifically manifesting as a predictable-filename weakness. This flaw allows a remote authenticated attacker to upload files containing attacker-controlled content to a known, predictable location on the local disk. In real-world attacks, threat actors (such as the group tracked as UTA0576) have chained this vulnerability with CVE-2026-104935 (an authentication bypass) and CVE-2026-111357 (a privilege escalation flaw) to gain unauthenticated root access to appliances and extract sensitive Active Directory credentials. Due to active exploitation in the wild, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-118527 to its Known Exploited Vulnerabilities (KEV) catalog on October 30, 2026. Ivanti has released security updates, such as Connect Secure versions 22.8R2.6 and 25.1.1.3, to address the issue.

CVE-2026-115560 is a remote code execution (RCE) vulnerability in PHP's session upload progress feature, which was disclosed by the PHP project in October 2026. The vulnerability stems from the inconsistent handling of session data when an application changes its serialization formats during request processing. It specifically affects environments where the `session.serialize_handler` is initially configured as `php_binary` or `php_serialize`, but is subsequently changed to `php` at runtime using `ini_set()` before `session_start()` is called, while the session upload progress feature remains active. Because this vulnerability requires a highly specific and uncommon combination of configuration settings and application code, the PHP security team has characterized it as an unlikely vector in practice. As a result, the issue is being addressed through PHP's routine release cycle rather than an emergency patch. Until a formal update is released, the recommended mitigation is to disable the session upload progress feature by setting `session.upload_progress.enabled = 0` in the PHP configuration.

CVE-2024-21413 is a remote code execution (RCE) vulnerability affecting Microsoft Outlook. It stems from improper input validation when Outlook processes URLs, particularly those using the `file://` protocol and crafted URL structures. This vulnerability, also known as the "MonikerLink" bug, allows attackers to bypass security protections, such as the Office Protected View, and execute arbitrary code on a victim's machine by sending a malicious email. The vulnerability can be triggered even when previewing a maliciously crafted email. Successful exploitation could lead to remote code execution, theft of NTLM credentials, data exfiltration, data encryption, installation of malware, and potential full system compromise. It affects various versions of Microsoft Outlook, including Microsoft Office 2016, 2019, 2021, and Microsoft 365 Apps.

CVE-2026-97229 is an integer overflow vulnerability (CWE-190) located in the CI/CD Regular Expression Compiler of GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw stems from insufficient validation of regular expressions used within project pipeline configurations. Under certain conditions, an unauthenticated remote attacker can exploit this vulnerability by supplying a specially crafted regular expression in a CI/CD configuration file (such as `.gitlab-ci.yml`), which can lead to arbitrary code execution on the affected GitLab server. The vulnerability affects self-managed GitLab versions 19.1 through 19.2.7, 19.3 through 19.3.3, and 19.4 through 19.4.1. Security researchers note that exploitation typically requires the ability to commit a configuration file to a repository. However, this constraint is bypassed on instances where self-registration and project creation are enabled for new users. GitLab has addressed the issue in versions 19.4.2, 19.3.4, and 19.2.8, and there have been no confirmed reports of active exploitation in the wild.

CVE-2026-76418 is a vulnerability affecting the Remote Access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software. The issue stems from logic errors—specifically an unchecked return value leading to a NULL pointer dereference—when secondary authentication is configured on a tunnel group. An unauthenticated, remote attacker can exploit this flaw by sending a crafted request while connecting to the SSL remote access VPN, which triggers an unexpected device reload and results in a denial of service (DoS) condition. A successful VPN login is not required to reach the vulnerable code path. In October 2026, Cisco's Product Security Incident Response Team (PSIRT) identified active exploitation of this vulnerability in the wild, prompting the Cybersecurity and Infrastructure Security Agency (CISA) to add it to its Known Exploited Vulnerabilities catalog. While Cisco has released software updates to resolve the issue, there are no official workarounds. Organizations unable to immediately apply the patches can temporarily mitigate the risk by disabling secondary authentication on the default or user-configured tunnel groups.