<?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 20:27:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07735</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07735</link>
      <description>bdu:2026-07735</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07735</guid>
    </item>
    <item>
      <title>BREW-mailcatcher-CVE-2026-34785 — Rack::Static prefix matching can expose unintended files under the static root</title>
      <link>https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-34785</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mailcatcher&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Static` determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as `&amp;#34;/css&amp;#34;`, it matches any request path that begins with that string, including unrelated paths such as `&amp;#34;/css-config.env&amp;#34;` or `&amp;#34;/css-backup.sql&amp;#34;`.&lt;/p&gt;
&lt;p&gt;As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`Rack::Static#route_file` performs static-route matching using logic equivalent to:&lt;/p&gt;
&lt;p&gt;```ruby
@urls.any? { |url| path.index(url) == 0 }
```&lt;/p&gt;
&lt;p&gt;This checks only whether the request path starts with the configured prefix string. It does not require a path segment boundary after the prefix.&lt;/p&gt;
&lt;p&gt;For example, with:&lt;/p&gt;
&lt;p&gt;```ruby
use Rack::Static, urls: [&amp;#34;/css&amp;#34;, &amp;#34;/js&amp;#34;], root: &amp;#34;public&amp;#34;
```&lt;/p&gt;
&lt;p&gt;the following path is matched as intended:&lt;/p&gt;
&lt;p&gt;```text
/css/style.css
```&lt;/p&gt;
&lt;p&gt;but these paths are also matched:&lt;/p&gt;
&lt;p&gt;```text
/css-config.env
/css-backup.sql
/csssecrets.yml
```&lt;/p&gt;
&lt;p&gt;If such files exist under the configured static root, Rack forwards the request to the file server and serves them as static content.&lt;/p&gt;
&lt;p&gt;This means a configuration intended to expose only directory trees such as `/css/...` and `/js/...` may also expose sibling files whose names begin with those same strings.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can request files under the configured static root whose names share a configured URL prefix and obtain their contents.&lt;/p&gt;
&lt;p&gt;In affected deployme…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mailcatcher&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Static` determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as `&amp;#34;/css&amp;#34;`, it matches any request path that begins with that string, including unrelated paths such as `&amp;#34;/css-config.env&amp;#34;` or `&amp;#34;/css-backup.sql&amp;#34;`.&lt;/p&gt;
&lt;p&gt;As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`Rack::Static#route_file` performs static-route matching using logic equivalent to:&lt;/p&gt;
&lt;p&gt;```ruby
@urls.any? { |url| path.index(url) == 0 }
```&lt;/p&gt;
&lt;p&gt;This checks only whether the request path starts with the configured prefix string. It does not require a path segment boundary after the prefix.&lt;/p&gt;
&lt;p&gt;For example, with:&lt;/p&gt;
&lt;p&gt;```ruby
use Rack::Static, urls: [&amp;#34;/css&amp;#34;, &amp;#34;/js&amp;#34;], root: &amp;#34;public&amp;#34;
```&lt;/p&gt;
&lt;p&gt;the following path is matched as intended:&lt;/p&gt;
&lt;p&gt;```text
/css/style.css
```&lt;/p&gt;
&lt;p&gt;but these paths are also matched:&lt;/p&gt;
&lt;p&gt;```text
/css-config.env
/css-backup.sql
/csssecrets.yml
```&lt;/p&gt;
&lt;p&gt;If such files exist under the configured static root, Rack forwards the request to the file server and serves them as static content.&lt;/p&gt;
&lt;p&gt;This means a configuration intended to expose only directory trees such as `/css/...` and `/js/...` may also expose sibling files whose names begin with those same strings.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can request files under the configured static root whose names share a configured URL prefix and obtain their contents.&lt;/p&gt;
&lt;p&gt;In affected deployme…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-34785</guid>
    </item>
    <item>
      <title>EUVD-2026-337303</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337303</link>
      <description>EUVD-2026-337303</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337303</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34785</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34785</link>
      <description>&lt;p&gt;Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as &amp;#34;/css&amp;#34;, it matches any request path that begins with that string, including unrelated paths such as &amp;#34;/css-config.env&amp;#34; or &amp;#34;/css-backup.sql&amp;#34;. As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as &amp;#34;/css&amp;#34;, it matches any request path that begins with that string, including unrelated paths such as &amp;#34;/css-config.env&amp;#34; or &amp;#34;/css-backup.sql&amp;#34;. As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34785</guid>
    </item>
    <item>
      <title>GHSA-h2jq-g4cq-5ppq — Rack::Static prefix matching can expose unintended files under the static root</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h2jq-g4cq-5ppq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Static` determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as `&amp;#34;/css&amp;#34;`, it matches any request path that begins with that string, including unrelated paths such as `&amp;#34;/css-config.env&amp;#34;` or `&amp;#34;/css-backup.sql&amp;#34;`.&lt;/p&gt;
&lt;p&gt;As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`Rack::Static#route_file` performs static-route matching using logic equivalent to:&lt;/p&gt;
&lt;p&gt;```ruby
@urls.any? { |url| path.index(url) == 0 }
```&lt;/p&gt;
&lt;p&gt;This checks only whether the request path starts with the configured prefix string. It does not require a path segment boundary after the prefix.&lt;/p&gt;
&lt;p&gt;For example, with:&lt;/p&gt;
&lt;p&gt;```ruby
use Rack::Static, urls: [&amp;#34;/css&amp;#34;, &amp;#34;/js&amp;#34;], root: &amp;#34;public&amp;#34;
```&lt;/p&gt;
&lt;p&gt;the following path is matched as intended:&lt;/p&gt;
&lt;p&gt;```text
/css/style.css
```&lt;/p&gt;
&lt;p&gt;but these paths are also matched:&lt;/p&gt;
&lt;p&gt;```text
/css-config.env
/css-backup.sql
/csssecrets.yml
```&lt;/p&gt;
&lt;p&gt;If such files exist under the configured static root, Rack forwards the request to the file server and serves them as static content.&lt;/p&gt;
&lt;p&gt;This means a configuration intended to expose only directory trees such as `/css/...` and `/js/...` may also expose sibling files whose names begin with those same strings.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can request files under the configured static root whose names share a configured URL prefix and obtain their contents.&lt;/p&gt;
&lt;p&gt;In affected deployme…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Static` determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as `&amp;#34;/css&amp;#34;`, it matches any request path that begins with that string, including unrelated paths such as `&amp;#34;/css-config.env&amp;#34;` or `&amp;#34;/css-backup.sql&amp;#34;`.&lt;/p&gt;
&lt;p&gt;As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`Rack::Static#route_file` performs static-route matching using logic equivalent to:&lt;/p&gt;
&lt;p&gt;```ruby
@urls.any? { |url| path.index(url) == 0 }
```&lt;/p&gt;
&lt;p&gt;This checks only whether the request path starts with the configured prefix string. It does not require a path segment boundary after the prefix.&lt;/p&gt;
&lt;p&gt;For example, with:&lt;/p&gt;
&lt;p&gt;```ruby
use Rack::Static, urls: [&amp;#34;/css&amp;#34;, &amp;#34;/js&amp;#34;], root: &amp;#34;public&amp;#34;
```&lt;/p&gt;
&lt;p&gt;the following path is matched as intended:&lt;/p&gt;
&lt;p&gt;```text
/css/style.css
```&lt;/p&gt;
&lt;p&gt;but these paths are also matched:&lt;/p&gt;
&lt;p&gt;```text
/css-config.env
/css-backup.sql
/csssecrets.yml
```&lt;/p&gt;
&lt;p&gt;If such files exist under the configured static root, Rack forwards the request to the file server and serves them as static content.&lt;/p&gt;
&lt;p&gt;This means a configuration intended to expose only directory trees such as `/css/...` and `/js/...` may also expose sibling files whose names begin with those same strings.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can request files under the configured static root whose names share a configured URL prefix and obtain their contents.&lt;/p&gt;
&lt;p&gt;In affected deployme…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h2jq-g4cq-5ppq</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10508-1 — ruby4.0-rubygem-rack-2.2-2.2.23-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10508-1</link>
      <description>&lt;p&gt;ruby4.0-rubygem-rack-2.2-2.2.23-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ruby4.0-rubygem-rack-2.2-2.2.23-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10508-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23321-1 — Security update for rmt-server</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23321-1</link>
      <description>&lt;p&gt;Security update for rmt-server&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for rmt-server&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23321-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-34785</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34785</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack, Ubuntu:25.10: ruby-rack, Ubuntu:26.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as &amp;#34;/css&amp;#34;, it matches any request path that begins with that string, including unrelated paths such as &amp;#34;/css-config.env&amp;#34; or &amp;#34;/css-backup.sql&amp;#34;. As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack, Ubuntu:25.10: ruby-rack, Ubuntu:26.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as &amp;#34;/css&amp;#34;, it matches any request path that begins with that string, including unrelated paths such as &amp;#34;/css-config.env&amp;#34; or &amp;#34;/css-backup.sql&amp;#34;. As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34785</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1687 — IBM License Metric Tool: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1687</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1687</guid>
    </item>
  </channel>
</rss>
