CVE-2026-6790 in Eclipse Jetty
In 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 enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.
Quick answer
Eclipse Foundation Eclipse Jetty should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Eclipse Jetty 9.4.0 through 9.4.60
- Eclipse Jetty 10.0.0 through 10.0.28
- Eclipse Jetty 11.0.0 through 11.0.28
- Eclipse Jetty 12.0.0 through 12.0.34
- Eclipse Jetty 12.1.0 through 12.1.8
Fixed versions
- Eclipse Jetty 9.4.61 or later
- Eclipse Jetty 10.0.29 or later
- Eclipse Jetty 11.0.29 or later
- Eclipse Jetty 12.0.35 or later
- Eclipse Jetty 12.1.9 or later
How to fix it
CVE-2026-6790 affects Eclipse Jetty. In simple terms, private headers or cookies may be sent to the wrong place. Fix it by updating to Eclipse Jetty 9.4.61 or later; Eclipse Jetty 10.0.29 or later; Eclipse Jetty 11.0.29 or later; Eclipse Jetty 12.0.35 or later; Eclipse Jetty 12.1.9 or later. If this system is online or used by admins, treat the fix as important.
- Find every place where Eclipse Jetty is installed or used.
- Check if the version matches: Eclipse Jetty 9.4.0 through 9.4.60; Eclipse Jetty 10.0.0 through 10.0.28; Eclipse Jetty 11.0.0 through 11.0.28; Eclipse Jetty 12.0.0 through 12.0.34; Eclipse Jetty 12.1.0 through 12.1.8.
- Update or apply the vendor fix: Eclipse Jetty 9.4.61 or later; Eclipse Jetty 10.0.29 or later; Eclipse Jetty 11.0.29 or later; Eclipse Jetty 12.0.35 or later; Eclipse Jetty 12.1.9 or later.
- If you cannot update today, allow only trusted users and trusted networks.
- Turn off the affected feature or plugin if the vendor says that is safe to do.
- Check logs for crashes, strange requests, new admin actions, or unexpected access.
- Change secrets or passwords if you think data or admin access may have been exposed.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version or mitigation matches: Eclipse Jetty 9.4.61 or later; Eclipse Jetty 10.0.29 or later; Eclipse Jetty 11.0.29 or later; Eclipse Jetty 12.0.35 or later; Eclipse Jetty 12.1.9 or later.
- Confirm the affected feature is no longer exposed to untrusted users.
- Run the affected workflow again and make sure it still works.
- Review logs again after the fix for repeated suspicious activity.
- Run a new Fixnx scan if this software is part of a public website.
- Save the advisory link and proof of the fix in your change record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-6790?
Eclipse Foundation Eclipse Jetty versions listed as affected should be reviewed: Eclipse Jetty 9.4.0 through 9.4.60, Eclipse Jetty 10.0.0 through 10.0.28, Eclipse Jetty 11.0.0 through 11.0.28, Eclipse Jetty 12.0.0 through 12.0.34, Eclipse Jetty 12.1.0 through 12.1.8.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.