CVE Tools

Jetty

80 CVEs tracked. 1 of them are in CISA KEV.

This hub aggregates every CVE we track for Jetty, a product in the networking infrastructure space. Use it to gauge the current risk picture and drill into individual advisories.

Jetty CVEs per month

Nov 2024 to Oct 2026. Point at a month, or focus the strip and use the arrow keys.
Jetty CVEs per month
MonthCVEs
2024-110
2024-120
2025-010
2025-020
2025-030
2025-040
2025-052
2025-060
2025-070
2025-081
2025-090
2025-100
2025-110
2025-120
2026-010
2026-020
2026-032
2026-042
2026-050
2026-060
2026-074
2026-081
2026-093
2026-103

Severity

How the 80 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • Critical57%
  • High2432%
  • Medium3649%
  • Low912%

Latest CVEs

The 15 most recently published vulnerabilities affecting Jetty.

  1. CVE-2026-77711When Jetty's `HttpClient` make a request to a server through a forward proxy, the server may reply with a 407 (Proxy Authentication Required). The client mistakenly interprets the 407 as coming ...—
  2. CVE-2026-76184In Eclipse Jetty, HttpClient may receive a redirect of the form: ``` /secure/../evil ``` If an attacker is able to control the redirects, then HttpClient matches authentication credenti...—
  3. CVE-2026-76182In Eclipse Jetty, `TryPathsHandler` and `TryFilesFilter` can be configured to forward requests to template URIs such as `index?p=$path`, where `$path` is the request path in context. However, UR...—
  4. CVE-2026-12611A client may issue HTTP/2 requests to a Jetty server that result in blocking writes that are never unblocked, eventually causing all threads to be blocked and the whole server to become unresponsiv...—
  5. CVE-2026-19203A client may issue specially crafted HTTP/1.1 chunked requests to a Jetty server that cause Jetty and an intermediary proxy to interpret different request boundaries, potentially resulting in HTTP ...—
  6. CVE-2026-19204A client may send a WebSocket frame with an unknown opcode and a very large declared payload length, causing Jetty to attempt a large memory allocation and potentially exhaust the JVM heap. Thi...—
  7. CVE-2026-10050Digest authentication lossy encoding9.1
  8. CVE-2024-7708For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow ...7.5
  9. CVE-2026-8384In Eclipse Jetty, an HTTP URI of this form: /public;/../admin/secret.txt results in an unresolved path of: /public/../admin/secret.txt instead of the expected: /admin...5.3
  10. CVE-2026-6790In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not...5.3
  11. CVE-2026-10051In Eclipse Jetty, a first HTTP/1.1 request with trailers causes the server to retain the trailers in subsequent requests performed over the same connection. Subsequent request that do not have trai...7.5
  12. CVE-2026-2332HTTP Request Smuggling via Chunked Extension Quoted-String Parsing7.4
  13. CVE-2026-5795In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable. Upon returning from the initial checks, there are conditions that cause an ...7.4
  14. CVE-2026-1605In Eclipse Jetty, versions 12.0.0-12.0.31 and 12.1.0-12.0.5, class GzipHandler exposes a vulnerability when a compressed HTTP request, with Content-Encoding: gzip, is processed and the correspondin...7.5
  15. CVE-2025-11143The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in secur...3.7

Product grouping is registry-driven, with AI assist and human review. How it works