Apache Tomcat 的 FORM 认证过程中存在授权不正确漏洞,允许绕过对资源访问的限制性安全约束(即限制用户只能通过 POST 方法访问资源,而不能通过 GET 方法)。 该问题影响以下版本的 Apache Tomcat:11.0.0-M1 至 11.0.24、10.1.0-M1 至 10.1.57、9.0.0-M1 至 9.0.120。 在创建此 CVE 时,以下版本已终止支持(EOL),但已知仍受影响:8.5.0 至 8.5.100、7.0.0 至 7.0.109。其他不受支持的版本也可能受到此漏洞影
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Apache Software Foundation | Apache Tomcat | 11.0.0-M1 ~ 11.0.24 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-73180 | Apache Tomcat: Authenticated WebSocket session survives end of HTTP session | |
| CVE-2026-68763 | Apache Tomcat: DoS via allocation leak in HTTP/2 backlog tracking when a stream is reset | |
| CVE-2026-68569 | Apache Tomcat: Principal lookup can fail open in some cases | |
| CVE-2026-66422 | Apache Tomcat: Servlet role references can bypass declarative role constraints | |
| CVE-2026-65927 | Apache Tomcat: RewriteValve [N] restarts at the second rule and may bypass access control | |
| CVE-2026-65905 | Apache Tomcat: Limited replay attack possible with DIGEST authentication | |
| CVE-2026-65637 | Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix in | |
| CVE-2026-65183 | Apache Tomcat: TOCTOU when setting specific permissions for Unix Domain Sockets | |
| CVE-2026-65182 | Apache Tomcat: Bypass longest prefix security constraint | |
| CVE-2026-49845 | Apache Hive: SQL Injection vulnerability in HiveMetaStore partition-name direct-SQL paths | |
| CVE-2026-55976 | Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on | |
| CVE-2026-53561 | Apache Hive: Unauthenticated authentication bypass in HiveServer2 HTTP SAML bearer-token v | |
| CVE-2026-49050 | Apache DolphinScheduler: General user can mint admin access tokens via /access-tokens |
No comments yet