<?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>Wed, 07 Oct 2026 13:04:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-39807 — Client-supplied URI scheme trusted without transport verification in bandit</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-39807</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mtrudel bandit&lt;/p&gt;
&lt;p&gt;Reliance on Untrusted Inputs in a Security Decision vulnerability in mtrudel bandit allows unauthenticated transport-state spoofing on plaintext HTTP connections.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.Pipeline&amp;#39;:determine_scheme/2 in lib/bandit/pipeline.ex returns the client-supplied URI scheme verbatim, ignoring the transport&amp;#39;s secure? flag. HTTP/1.1 absolute-form request targets (e.g. GET https://victim/path HTTP/1.1) and the HTTP/2 :scheme pseudo-header are both attacker-controlled strings that flow through this function. Over a plaintext TCP connection, a client can declare https and Bandit will set conn.scheme = :https even though no TLS was negotiated.&lt;/p&gt;
&lt;p&gt;Downstream Plug consumers that branch on conn.scheme are silently misled: Plug.SSL&amp;#39;s already-secure branch skips its HTTP→HTTPS redirect, cookies emitted with secure: true are sent over plaintext, audit logs record requests as having arrived over HTTPS, and CSRF/SameSite gating may make incorrect decisions.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 1.0.0 before 1.11.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mtrudel bandit&lt;/p&gt;
&lt;p&gt;Reliance on Untrusted Inputs in a Security Decision vulnerability in mtrudel bandit allows unauthenticated transport-state spoofing on plaintext HTTP connections.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.Pipeline&amp;#39;:determine_scheme/2 in lib/bandit/pipeline.ex returns the client-supplied URI scheme verbatim, ignoring the transport&amp;#39;s secure? flag. HTTP/1.1 absolute-form request targets (e.g. GET https://victim/path HTTP/1.1) and the HTTP/2 :scheme pseudo-header are both attacker-controlled strings that flow through this function. Over a plaintext TCP connection, a client can declare https and Bandit will set conn.scheme = :https even though no TLS was negotiated.&lt;/p&gt;
&lt;p&gt;Downstream Plug consumers that branch on conn.scheme are silently misled: Plug.SSL&amp;#39;s already-secure branch skips its HTTP→HTTPS redirect, cookies emitted with secure: true are sent over plaintext, audit logs record requests as having arrived over HTTPS, and CSRF/SameSite gating may make incorrect decisions.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 1.0.0 before 1.11.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-39807</guid>
    </item>
  </channel>
</rss>
