406 matches found
CVE-2026-86350
Inconsistent interpretation of HTTP/2 requests 'HTTP Request/Response smuggling' vulnerability in Apache Tomcat caused by a regression in fix for CVE-2026-41293 can trigger request header mix-up. This issue affects Apache Tomcat: from 11.0.22 through 11.0.25, from 10.1.55 through 10.1.59, from...
CLSA-2026-1790158682 Fix CVE(s): CVE-2026-49975
SECURITY UPDATE: denial of service via an unbounded number of HTTP/2 request header lines - debian/patches/CVE-2026-49975.patch: add the maxheaders directive default 1000 and enforce it in ngxhttpprocessrequestheaders and ngxhttpv2stateprocessheader, so a client can no longer drive unbounded...
CVE-2026-86350: Inconsistent Interpretation of HTTP Requests
Inconsistent interpretation of HTTP/2 requests 'HTTP Request/Response smuggling' vulnerability in Apache Tomcat caused by a regression in fix for CVE-2026-41293 can trigger request header mix-up. This issue affects Apache Tomcat: from 11.0.22 through 11.0.25, from 10.1.55 through 10.1.59, from...
CVE-2026-86350: Inconsistent Interpretation of HTTP Requests
Inconsistent interpretation of HTTP/2 requests 'HTTP Request/Response smuggling' vulnerability in Apache Tomcat caused by a regression in fix for CVE-2026-41293 can trigger request header mix-up. This issue affects Apache Tomcat: from 11.0.22 through 11.0.25, from 10.1.55 through 10.1.59, from...
PT-2026-97299
Name of the Vulnerable Software and Affected Versions Apache Tomcat versions 11.0.22 through 11.0.25 Apache Tomcat versions 10.1.55 through 10.1.59 Apache Tomcat versions 9.0.118 through 9.0.121 Description An inconsistent interpretation of HTTP/2 requests, known as HTTP Request/Response smugglin...
Fixed in Apache Tomcat 11.0.26
Low: WebSocket message smuggling with per-message-deflate CVE-2026-87022 Improper handling of length parameter allows WebSocket message smuggling when per-message-deflate is used. This was fixed with commit 4fef25fe. This issue was reported to the Tomcat security team on 7 September 2026. The iss...
Fixed in Apache Tomcat 9.0.122
Low: WebSocket message smuggling with per-message-deflate CVE-2026-87022 Improper handling of length parameter allows WebSocket message smuggling when per-message-deflate is used. This was fixed with commit 959a52a2. This issue was reported to the Tomcat security team on 7 September 2026. The iss...
Fixed in Apache Tomcat 10.1.60
Low: WebSocket message smuggling with per-message-deflate CVE-2026-87022 Improper handling of length parameter allows WebSocket message smuggling when per-message-deflate is used. This was fixed with commit 567a8551. This issue was reported to the Tomcat security team on 7 September 2026. The iss...
CVE-2026-90447: Authentication Bypass by Spoofing
A routing rule selects between two different authentication mechanisms for the same downstream service based on the value of a client-supplied request header, rather than on any property the client cannot control. An authenticated user in possession of a shared service credential can set this...
No title provided
A flaw was found in quarkus-spring-web. A remote attacker could exploit this vulnerability by manipulating the URL query string. The system incorrectly reads the URL query string as a request header, which can lead to an authorization bypass, allowing unauthorized access to resources...
CVE-2026-19651
A flaw was found in quarkus-spring-web. A remote attacker could exploit this vulnerability by manipulating the URL query string. The system incorrectly reads the URL query string as a request header, which can lead to an authorization bypass, allowing unauthorized access to resources. Mitigation...
EUVD-2026-66748
AntFlow V2.0.0 is vulnerable to Incorrect Access Control. JiMuMDCCommonsRequestLoggingFilter.java retrieves the userid from the request header as the core of the identity verification mechanism, allowing attackers to forge any user identity credential information, thereby causing sensitive...
CVE-2026-77775
Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. resolveopenaiupstreambase in headroom/proxy/handlers/openai.py accepts the header value, requires only that it parse with an http or https scheme and a hostname, and returns it for use ...
CVE-2026-68005
An issue in ACME minihttpd 1.30 and prior allows a remote attacker to cause a denial of service via the HTTP request header parser in the handlerequest function...
PT-2026-76774
Name of the Vulnerable Software and Affected Versions ACME mini httpd versions prior to 1.31 Description A remote attacker can cause a denial of service through the HTTP request header parser within the handle request function. Recommendations Update ACME mini httpd to version 1.31 or later. As a...
CVE-2026-68005: Uncontrolled Resource Consumption
An issue in ACME minihttpd 1.30 and prior allows a remote attacker to cause a denial of service via the HTTP request header parser in the handlerequest function...
CVE-2026-73286 RustF: Request headers can populate server-derived IAM condition keys, letting a caller satisfy identity-based policy conditions
RustFS is a distributed object storage system built in Rust. Prior to 1.0.0-beta.12, RustFS getconditionvalues folds attacker-controlled request headers from HeaderMap into server-derived userid, username, principaltype, groups, versionid, signatureversion, jwt:, and ldap: condition keys, allowin...
EUVD-2026-53608
A path traversal vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to delete arbitrary files and directories on the instance, including the entire user storage directory containing Git LFS objects, release assets, attachments, and avatars. The...
CVE-2026-16328
In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an...
CVE-2026-16328: Server-Side Request Forgery (SSRF)
In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an...