Skip to content
Fencer Intel
high 8.2

CVE-2026-77711 json

Jetty HttpClient accepts proxy authentication challenges from an HTTPS origin and discloses proxy credentials inside the tunnel

published 27d ago modified 27d ago also EUVD-2026-101947 , GHSA-r2c5-3p8g-wpvw

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository jetty/jetty.project. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
8.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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.

Patch / fix

  • org.eclipse.jetty jetty-client 9.4.65, 10.0.33, 11.0.33, 12.0.39, 12.1.13
  • eclipse jetty 9.4.65, 10.0.33, 11.0.33, 12.0.39, 12.1.13
  • jetty12 Debian 14 12.0.39-1

debian advisories DEBIAN-CVE-2026-77711

Is CVE-2026-77711 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-77711 updated cvss 7.5

org.eclipse.jetty/jetty-client: jetty-client: Information disclosure via improper proxy authentication handling

  • Red Hat build of Apache Camel - HawtIO 4 jetty-client 12.1.11.redhat-00001 Red Hat build of Apache Camel 4 for Quarkus 3 jetty-client 12.1.11.redhat-00001 Red Hat build of Apache Camel for Spring Boot 4 jetty-client 12.1.11.redhat-00001 Red Hat build of Apicurio Registry 3 jetty-client 12.1.11.redhat-00001 Red Hat build of Debezium 3 jetty-client 12.1.11.redhat-00001 Red Hat Enterprise Linux 7 maven-site-plugin-javadoc, maven-site-plugin 3.2-7.el7
    +4 more products
    Red Hat Enterprise Linux 9 jmc Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9 Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Satellite 6 openvox-server 8.15.2-1.el9sat
    affected: workaround, no fix available
  • Red Hat Build of Apache Camel 3.33.4.SP3 jetty-client 12.1.14.redhat-00001
    fixed: vendor fix RHSA-2026:95622
  • Red Hat Build of Apache Camel 3.33.4.SP3 jimfs 1.1, jna 5.8.0, bcel 6.7.0, gax 2.74.1, icu4j 78.2, joni 2.2.6, +1616 more
    not affected: vulnerable code not present
  • Red Hat Fuse 7 jetty-client 12.1.11.redhat-00001
    not affected: component not present
  • Red Hat Offline Knowledge Portal offline-knowledge-portal/rhokp-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-th-torch-cpu-py312-rhel9, rhoai/odh-th-torch-cuda-py312-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-cpu-torch291-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, +1 more
    not affected: vulnerable code not in execute path
  • Red Hat streams for Apache Kafka 3 jetty-client 12.1.11.redhat-00001
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
27d ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/jetty/jetty.project/security/advisories/GHSA-r2c5-3p8g-wpvw referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA 4.0 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • Eclipse Foundation Eclipse Jetty

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of jetty/jetty.project published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.