Jetty invalid URI parsing may produce invalid HttpURI.authority

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

2.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2022-2047: 1.32% estimated exploitation activity in the next 30 days; percentile 70.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description URI use within Jetty's HttpURI class can parse invalid URIs such as http://localhost;/path as having an authority with a host of localhost;. A URIs of the type http://localhost;/path should be interpreted to be either invalid or as localhost; to be the userinfo and no host. However, HttpURI.host returns localhost; which is definitely wrong. Impact This can lead to errors with Jetty's HttpClient, and Jetty's ProxyServlet / AsyncProxyServlet / AsyncMiddleManServlet wrongly interpreting an authority with no host as one with a host. Patches Patched in PR #8146 for Jetty version 9.4.47. Patched in PR #8014 for Jetty versions 10.0.10, and 11.0.10 Workarounds None. For more information If you have any questions or comments about this advisory: Email us at security@webtide.com.

Published by the source

7 Jul 2022, 20:55 UTC

Last modified by the source

29 Jan 2023, 05:06 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cj7v-27pg-wf7q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-2047

Advisory: Jetty invalid URI parsing may produce invalid HttpURI.authority
IDs: CVE-2022-2047, GHSA-cj7v-27pg-wf7q
Record: https://patchnext.com/advisories/cve-2022-2047 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty:jetty-http 11.0.10, 10.0.10, 9.4.47. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty:jetty-http: affected < 9.4.47; >= 10.0.0, < 10.0.10; >= 11.0.0, < 11.0.10; fixed in 11.0.10, 9.4.47, 10.0.10

## Suggested inspection (read-only)
- Maven org.eclipse.jetty:jetty-http: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty:jetty-http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cj7v-27pg-wf7q (GitHub-reviewed advisory GHSA-cj7v-27pg-wf7q lists affected ranges: Maven org.eclipse.jetty:jetty-http >=0 =10.0.0 =11.0.0 <11.0.10)

Commands are suggestions: review each one before running it.