What's new: New story (first merged summary): ten coordinated Apache advisories covering 7 Tomcat CVEs and 3 Tomcat Native CVEs were published to oss-security within roughly 30 minutes on 2026-09-23. Two entries are follow-on flaws to earlier 2026 fixes: CVE-2026-86248 (incomplete fix for CVE-2026-34500) and CVE-2026-86350 (regression in the fix for CVE-2026-41293). No exploitation has been reported for any…
Merged summary · glm-5.3 · rewritten as coverage arrives
Ten advisories posted to oss-security on 2026-09-23 cover seven Apache Tomcat CVEs (WebSocket security-constraint bypass, WebSocket and AJP DoS, CRL/OCSP revocation gaps, HTTP/2 request-header mix-up) and three Apache Tomcat Native CVEs (TLS-handshake JVM…
Between 16:28 and 16:59 UTC on 2026-09-23, oss-security carried ten coordinated Apache security advisories: seven for Apache Tomcat and three for Apache Tomcat Native. The important-rated issues are CVE-2026-76183 (bypass of security constraints on any WebSocket endpoint), CVE-2026-77791 (busy-wait denial of service when sending a WebSocket close message), CVE-2026-78383 (an unauthenticated AJP request missing its body pins an AJP processing thread via unbounded resource allocation), CVE-2026-86350 (a regression in the fix for CVE-2026-41293 causing HTTP/2 request-header mix-up), and CVE-2026-86243 (a Tomcat Native buffer over-read during the TLS handshake that can crash the JVM). The moderate-rated issues are CVE-2026-73581 (OpenSSL and OpenSSL-FFM TLS implementations ignore CRLs when the certificate is loaded from a keystore), CVE-2026-79677 (a lost asynchronous WebSocket write timeout leaves a resource unreleased past its effective lifetime), CVE-2026-86248 (an incomplete fix for CVE-2026-34500 in which OCSP checks can soft-fail via the FFM path even when soft-fail is disabled, so CLIENT_CERT authentication may not fail as expected), CVE-2026-86246 (Tomcat Native initializes TLS with insecure OpenSSL defaults including ALLOW_CLIENT_RENEGOTIATION, NO_EXTENDED_MASTER_SECRET, IGNORE_UNEXPECTED_EOF, and ALLOW_NO_DHE_KEX), and CVE-2026-86247 (a race condition that can downgrade client-certificate verification requirements). Most Tomcat CVEs share upper bounds of 11.0.25, 10.1.59, 9.0.121, and 8.5.100, with several DoS and bypass issues extending down through 7.0.x; the two revocation follow-ups and the HTTP/2 regression affect only recent releases. The three Tomcat Native CVEs affect 1.3.0-1.3.8 and 2.0.0-2.0.15, with unsupported earlier versions possibly affected. Mark Thomas is the named discloser on five of the ten advisories. No advisory reports exploitation in the wild, and the posts do not state fixed version numbers. The reports do not conflict with one another; their affected-version ranges simply differ per CVE.
Batch of 10 advisories posted to oss-security on 2026-09-23 between 16:28:37 and 16:59:11 UTC: 7 for Apache Tomcat and 3 for Apache Tomcat Native; 5 rated important, 5 rated moderate.
CVE-2026-73581 (moderate, Tomcat): OpenSSL and OpenSSL-FFM TLS implementations ignore CRLs when the certificate is loaded from a keystore; affects 11.0.0-M1-11.0.25, 10.1.0-M1-10.1.59, 9.0.0.M1-9.0.121, and 8.5 through 8.5.100 (releases…
Improper Input Validation vulnerability in Apache Tomcat
CVE-2026-76183 (important, Tomcat): authentication bypass lets attackers bypass security constraints on any WebSocket endpoint; affects 11.0.0-M1-11.0.25, 10.1.0-M1-10.1.59, 9.0.0.M1-9.0.121, 8.5.0-8.5.100, 7.0.43-7.0.109, plus releases…
CVE-2026-77791 (important, Tomcat): busy wait while sending a WebSocket close message enables denial of service; affects 11.0.0-M5-11.0.25, 10.1.8-10.1.59, 9.0.74-9.0.121, 8.5.88-8.5.100, and Tomcat through 7.0.109.
CVE-2026-78383 (important, Tomcat): unauthenticated AJP request that omits its body pins an AJP processing thread through unbounded resource allocation; affects 11.0.0-M1-11.0.25, 10.1.0-M1-10.1.59, 9.0.0.M1-9.0.121, 8.5.0-8.5.100, and…
CVE-2026-79677 (moderate, Tomcat): resource not released after its effective lifetime when an asynchronous WebSocket write timeout is lost; affects 11.0.0-M1-11.0.25, 10.1.0-M1-10.1.59, 9.0.0.M1-9.0.121, 8.5.0-8.5.100, and 7.0.43-7.0.109…
CVE-2026-86248 (moderate, Tomcat): incomplete fix for CVE-2026-34500; with the foreign-function memory (FFM) path some OCSP checks soft-fail even when soft-fail is disabled, so CLIENT_CERT authentication does not fail as expected; affects…
CVE-2026-86350 (important, Tomcat): regression in the fix for CVE-2026-41293 causes inconsistent HTTP/2 request interpretation and request-header mix-up; affects 11.0.22-11.0.25, 10.1.55-10.1.59, and 9.0.118-9.0.121.
Apache Tomcat CVE-2026-76183 lets attackers bypass security constraints on any WebSocket endpoint.
CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat
CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.
Improper Input Validation vulnerability in Apache Tomcat
Improper Input Validation vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 10.0.0-M1 through 10.0.27. Older, end of support versions may also be affected. Users are recommended to upgrade to version [FIXED_VERSION], which fixes the issue.
Critical Authentication Bypass in Apache Tomcat WebSocket Endpoints
CVE-2026-76183 is a critical authentication bypass vulnerability in Apache Tomcat that allows an attacker to bypass security constraints for any configured WebSocket endpoint. The flaw is triggered by making requests using alternate, malformed hostnames that the server accepts but do not match the intended security constraints. A successful attack grants unauthorized access to protected WebSocket resources without authentication, potentially leading to data exposure or manipulation. This issue affects a wide range of supported and older, unsupported Tomcat versions. As of this analysis, there are no known public exploits or reports of in-the-wild exploitation.
Do: Upgrade to Apache Tomcat 11.0.26, 10.1.60, or 9.0.122 immediately. For older, unsupported versions (8.5.x, 7.0.x), upgrade to a supported release. There is no other mitigation for this authentication bypass.
WebSocket Async Write Timeout DoS in Apache Tomcat
Apache Tomcat mishandles the timeouts that govern asynchronous WebSocket writes, due to a missing release of resources after their effective lifetime combined with a comparison using wrong factors (CWE-772/CWE-1025). A malicious or misbehaving WebSocket client can cause these write timeouts to be lost, so connections, buffers, and associated server resources are never cleaned up and accumulate on the server. The impact is denial of service against applications hosting WebSocket endpoints, not data disclosure or code execution. All currently supported Tomcat branches are affected (11.0.0-M1–11.0.25, 10.1.0-M1–10.1.59, 9.0.0.M1–9.0.121), plus the EOL 8.5.0–8.5.100 and 7.0.43–7.0.109 ranges. There is no CVSS score yet, no public proof of concept, and no known exploitation in the wild.
Do: Upgrade to Apache Tomcat 11.0.26, 10.1.60, or 9.0.122 depending on your branch; deployments on EOL 8.5.x or 7.0.x cannot receive a fix and should migrate to a supported release. If immediate patching is not possible, enforce authentication and rate limits on WebSocket endpoints, cap concurrent WebSocket connections per client, and alert on long-lived or stuck async-write sessions. After patching, verify that WebSocket write timeouts now fire correctly under load testing.
7.5
group max
—
Apache Tomcat 11.0.0-M1 through 11.0.25
Apache Tomcat 10.1.0-M1 through 10.1.59
Apache Tomcat 9.0.0.M1 through 9.0.121
+2 more
from 11.0.0-M1 through 11.0.25
Apache Software Foundation Apache Tomcat from 10.1.0-M1 through 10.1.59
Apache Software Foundation Apache Tomcat from 9.0.0.M1 through 9.0.121
+2 more
massUnknown, but likely a large proportion of the estimated 700k+ public Tomcat servers
mass≈1M+ internet-reachable Tomcat instances plausibly running affected versions, of which only the WebSocket-enabled subset is practically exploitable