Eclipse Jetty
Approved changes feed: RSS · Atom
cpe:2.3:a:eclipse_foundation:eclipse_jetty:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Eclipse Foundation (2c315c48-0111-5572-bbde-cc70cfafb2e9) |
|---|---|
| Product | Eclipse Jetty (af35049f-115c-5785-a574-2576d1aef086) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-76182 |
vulnerable | 2026-11-03 10:15:36.097648 |
Details available
In 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, URI paths may contain characters that are reserved in URI queries so that a path of `/s&a=1` when applied to the template becomes `index?p=/s&a=1`, which is interpreted as 2 query parameters: `p=/s` and `a=1`, rather than just one query parameter `p` whose value is `/s&a=1`.
Published: 2026-10-15T08:40:58.439Z
Updated: 2026-10-15T13:59:12.521Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-76184 |
vulnerable | 2026-11-03 10:15:36.020568 |
Details available
In 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 credentials against `/secure` rather than normalizing the path to `/evil`, and will therefore follow the redirect sending the `Authorization` header for `/secure` to `/evil`.
This also mean that the attacker must have an evil application deployed on the same domain as the target.
Published: 2026-10-15T08:46:54.683Z
Updated: 2026-10-15T13:51:45.344Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-77711 |
vulnerable | 2026-11-03 10:15:17.532423 |
Details available
When 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 from the proxy, so it re-sends the request with the `Proxy-Authentication` header, which arrives to the server, that now has access to the proxy credentials.
Published: 2026-10-15T08:51:48.066Z
Updated: 2026-10-15T13:50:52.566Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-19204 |
vulnerable | 2026-09-16 04:34:15.636159 |
Details available
A 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.
This occurs when auto-fragmentation is enabled, as unknown opcodes bypass the normal maximum frame size handling and payload allocation occurs before the opcode is validated.
Published: 2026-09-07T10:19:24.186Z
Updated: 2026-09-08T15:06:46.810Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-19203 |
vulnerable | 2026-09-16 04:34:15.468848 |
Details available
A 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 request smuggling.
This is caused by Jetty accepting a lone LF character as a terminator in parts of chunked request parsing. Depending on the Jetty version and configured HTTP compliance mode, this may occur in chunk extensions, chunk data termination, or trailer termination.
Published: 2026-09-08T12:08:37.576Z
Updated: 2026-09-08T14:21:55.816Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-12611 |
vulnerable | 2026-09-16 04:32:50.840834 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-10050 |
vulnerable | 2026-09-16 04:32:43.104832 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-8384 |
vulnerable | 2026-07-29 01:09:05.827209 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6790 |
vulnerable | 2026-07-29 01:06:21.179714 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-10051 |
vulnerable | 2026-07-29 00:20:51.812799 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-7708 |
vulnerable | 2026-07-28 23:07:12.465736 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-5795 |
vulnerable | 2026-06-08 08:07:04.108688 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2332 |
vulnerable | 2026-06-08 07:55:16.918578 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1605 |
vulnerable | 2026-06-08 07:49:09.019999 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-11143 |
vulnerable | 2026-06-08 07:02:28.146858 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.