NGINX released versions 1.30.6 and 1.31.7 on October 14, 2026, fixing five medium-severity vulnerabilities affecting its web server. Three involve memory errors that could crash worker processes or potentially allow code execution, while another could enable forged TLS sessions to bypass client-certificate verification. The fifth affects HTTP/3, allowing extra bytes to be injected into proxied requests. F5, NGINX’s parent company, rated the three memory flaws Critical, with CVSS v4.0 scores of 9.2, and scored the TLS and HTTP/3 vulnerabilities 8.3 and 6.9, respectively. As of October 15, none appeared in CISA’s Known Exploited Vulnerabilities catalog, and neither NGINX nor F5 reported active exploitation. The vulnerabilities require specific configurations to be exploitable. CVE-2026-15176 affects locations combining an alias directive with a URI-changing rewrite and references to $request_filename. CVE-2026-93479 involves regex-map captures used by root or log_format, while CVE-2026-97205 affects certain configurations using asynchronous I/O (AIO) and Server Side Includes (SSI). CVE-2026-97629 concerns automatic TLS session-ticket key rotation when a shared session cache is enabled without explicitly configured ticket keys. The flaw could permit a forged session to bypass client-certificate checks, although F5 says successful forgery is non-deterministic and beyond an attacker’s control. The HTTP/3 vulnerability, CVE-2026-95101, occurs when an unknown frame is split across reads, causing leftover frame-length data to be treated as request-body content and forwarded to a backend. This can bypass the client_max_body_size check. The issue affects configurations using HTTP/3 with proxy_request_buffering enabled, which is the default. Another vulnerability, CVE-2026-93479, is linked to string-handling changes introduced in July’s security fixes. Administrators should upgrade to NGINX 1.30.6 (stable) or 1.31.7 (mainline). If upgrading is not immediately possible, F5 recommends configuration-specific mitigations, including removing affected alias directives, disabling AIO or SSI, disabling proxy request buffering for HTTP/3, and explicitly configuring TLS ticket keys. Administrators should inspect their active configuration using nginx -T. Older branches and distribution packages may remain vulnerable unless patches have been backported.
Cybersecurity researchers from Group-IB and NyxLab have uncovered a large-scale cyberattack campaign targeting exposed network edge devices, including Fortinet FortiGate and Palo A...
Japanese video game developer Capcom has confirmed a data breach affecting more than 11.7 million CAPCOM ID accounts. Exposed information includes email addresses, account creation...
Security teams are assessing increased exposure after public exploit demonstrations appeared for two severe PHP flaws, identified as CVE-2026-109618 and CVE-2026-109619. Referred t...