<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 15:21:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-30448</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-30448</link>
      <description>EUVD-2026-30448</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-30448</guid>
    </item>
    <item>
      <title>fkie_cve-2021-39155</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-39155</link>
      <description>&lt;p&gt;Istio is an open source platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed. As an example, the user may have an authorization policy that rejects request with hostname &amp;#34;httpbin.foo&amp;#34; for some source IPs, but the attacker can bypass this by sending the request with hostname &amp;#34;Httpbin.Foo&amp;#34;. Patches are available in Istio 1.11.1, Istio 1.10.4 and Istio 1.9.8. As a work around a Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Istio is an open source platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed. As an example, the user may have an authorization policy that rejects request with hostname &amp;#34;httpbin.foo&amp;#34; for some source IPs, but the attacker can bypass this by sending the request with hostname &amp;#34;Httpbin.Foo&amp;#34;. Patches are available in Istio 1.11.1, Istio 1.10.4 and Istio 1.9.8. As a work around a Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-39155</guid>
    </item>
    <item>
      <title>GHSA-7774-7vr3-cc8j — Authorization Policy Bypass Due to Case Insensitive Host Comparison</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7774-7vr3-cc8j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: istio.io/istio&lt;/p&gt;
&lt;p&gt;### Impact
According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive.  The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.
 
As an example, the user may have an authorization policy that rejects request with hostname &amp;#34;httpbin.foo&amp;#34; for some source IPs, but the attacker can bypass this by sending the request with hostname &amp;#34;Httpbin.Foo&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above&lt;/p&gt;
&lt;p&gt;### Workarounds
A Lua filter may be written to normalize Host header before the authorization check.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.&lt;/p&gt;
&lt;p&gt;### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: istio.io/istio&lt;/p&gt;
&lt;p&gt;### Impact
According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive.  The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.
 
As an example, the user may have an authorization policy that rejects request with hostname &amp;#34;httpbin.foo&amp;#34; for some source IPs, but the attacker can bypass this by sending the request with hostname &amp;#34;Httpbin.Foo&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above&lt;/p&gt;
&lt;p&gt;### Workarounds
A Lua filter may be written to normalize Host header before the authorization check.  This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.&lt;/p&gt;
&lt;p&gt;### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7774-7vr3-cc8j</guid>
    </item>
    <item>
      <title>gsd-2021-39155</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-39155</link>
      <description>gsd-2021-39155</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-39155</guid>
    </item>
    <item>
      <title>RHSA-2021:3272 — Red Hat Security Advisory: Red Hat OpenShift Service Mesh 2.0.7.1 security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2021:3272</link>
      <description>&lt;p&gt;envoyproxy/envoy: HTTP request with multiple value headers can bypass authorization policies envoyproxy/envoy: HTTP request with a URL fragment in the URI can bypass authorization policies envoyproxy/envoy: denial of service when using extensions that modify request or response sizes istio/istio: HTTP request can bypass authorization mechanisms due to case insensitive host comparison istio/istio: HTTP request with fragment in URI can bypass authorization mechanisms&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;envoyproxy/envoy: HTTP request with multiple value headers can bypass authorization policies envoyproxy/envoy: HTTP request with a URL fragment in the URI can bypass authorization policies envoyproxy/envoy: denial of service when using extensions that modify request or response sizes istio/istio: HTTP request can bypass authorization mechanisms due to case insensitive host comparison istio/istio: HTTP request with fragment in URI can bypass authorization mechanisms&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2021:3272</guid>
    </item>
  </channel>
</rss>
