<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 02:16:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-6790</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-6790</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse Jetty&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112).&lt;/p&gt;
&lt;p&gt;This mismatch can cause a number of problems that may be classified as vulnerabilities such as:&lt;/p&gt;
&lt;p&gt;*  
        
      URI constructions (for example, for redirects -- this is typical for login pages)&lt;/p&gt;
&lt;p&gt;*  
        
      Virtual host selection&lt;/p&gt;
&lt;p&gt;*  
        
      Reverse proxying&lt;/p&gt;
&lt;p&gt;*  
        
      Misleading logs&lt;/p&gt;
&lt;p&gt;*  
        
      Etc.&lt;/p&gt;
&lt;p&gt;Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse Jetty&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112).&lt;/p&gt;
&lt;p&gt;This mismatch can cause a number of problems that may be classified as vulnerabilities such as:&lt;/p&gt;
&lt;p&gt;*  
        
      URI constructions (for example, for redirects -- this is typical for login pages)&lt;/p&gt;
&lt;p&gt;*  
        
      Virtual host selection&lt;/p&gt;
&lt;p&gt;*  
        
      Reverse proxying&lt;/p&gt;
&lt;p&gt;*  
        
      Misleading logs&lt;/p&gt;
&lt;p&gt;*  
        
      Etc.&lt;/p&gt;
&lt;p&gt;Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-6790</guid>
    </item>
  </channel>
</rss>
