<?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 09:33:07 +0000</lastBuildDate>
    <item>
      <title>CLEANSTART-2026-CK66622 — Security fix for CVE-2026-47737 applied in: logstash-fips 9.4.3-r1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ck66622</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: logstash-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the logstash-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: logstash-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the logstash-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ck66622</guid>
    </item>
    <item>
      <title>EUVD-2026-337961</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337961</link>
      <description>EUVD-2026-337961</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337961</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47737</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47737</link>
      <description>&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47737</guid>
    </item>
    <item>
      <title>GHSA-2vqw-3mp8-cgmx — Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2vqw-3mp8-cgmx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: puma&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Puma is vulnerable to source IP spoofing when `set_remote_address proxy_protocol: :v1` is enabled and persistent connections are used.&lt;/p&gt;
&lt;p&gt;PROXY protocol v1 is a connection-level protocol. [Support was added to Puma in v5.5.0](https://github.com/puma/puma/issues/2651). A proxy sends one PROXY header at the beginning of a TCP connection, before any HTTP data. Puma incorrectly re-parsed PROXY protocol headers after each keep-alive request on the same connection. An attacker able to send HTTP requests through a trusted proxy could therefore inject a second PROXY header between HTTP requests. Puma would treat the injected header as authoritative for the next request and overwrite `REMOTE_ADDR`.&lt;/p&gt;
&lt;p&gt;This can mislead applications or middleware that use `REMOTE_ADDR` for security decisions, rate limiting, auditing, or allow/deny lists.&lt;/p&gt;
&lt;p&gt;**Only deployments that explicitly enable PROXY protocol v1 are affected**, and will have set:&lt;/p&gt;
&lt;p&gt;```ruby
set_remote_address proxy_protocol: :v1
```&lt;/p&gt;
&lt;p&gt;Puma&amp;#39;s default configuration is not affected. Deployments that do not use persistent connections to Puma are also not expected to be affected by this issue.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users should upgrade to versions 7.2.1 or 8.0.2.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable PROXY protocol v1 parsing if it is not required:&lt;/p&gt;
&lt;p&gt;```ruby
   # remove/comment this:
   # set_remote_address proxy_protocol: :v1
 ```&lt;/p&gt;
&lt;p&gt;Users can also disable persistent connections to Puma, for example:&lt;/p&gt;
&lt;p&gt;```ruby
enable_keep_alives false
```&lt;/p&gt;
&lt;p&gt;### References…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: puma&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Puma is vulnerable to source IP spoofing when `set_remote_address proxy_protocol: :v1` is enabled and persistent connections are used.&lt;/p&gt;
&lt;p&gt;PROXY protocol v1 is a connection-level protocol. [Support was added to Puma in v5.5.0](https://github.com/puma/puma/issues/2651). A proxy sends one PROXY header at the beginning of a TCP connection, before any HTTP data. Puma incorrectly re-parsed PROXY protocol headers after each keep-alive request on the same connection. An attacker able to send HTTP requests through a trusted proxy could therefore inject a second PROXY header between HTTP requests. Puma would treat the injected header as authoritative for the next request and overwrite `REMOTE_ADDR`.&lt;/p&gt;
&lt;p&gt;This can mislead applications or middleware that use `REMOTE_ADDR` for security decisions, rate limiting, auditing, or allow/deny lists.&lt;/p&gt;
&lt;p&gt;**Only deployments that explicitly enable PROXY protocol v1 are affected**, and will have set:&lt;/p&gt;
&lt;p&gt;```ruby
set_remote_address proxy_protocol: :v1
```&lt;/p&gt;
&lt;p&gt;Puma&amp;#39;s default configuration is not affected. Deployments that do not use persistent connections to Puma are also not expected to be affected by this issue.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users should upgrade to versions 7.2.1 or 8.0.2.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable PROXY protocol v1 parsing if it is not required:&lt;/p&gt;
&lt;p&gt;```ruby
   # remove/comment this:
   # set_remote_address proxy_protocol: :v1
 ```&lt;/p&gt;
&lt;p&gt;Users can also disable persistent connections to Puma, for example:&lt;/p&gt;
&lt;p&gt;```ruby
enable_keep_alives false
```&lt;/p&gt;
&lt;p&gt;### References…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2vqw-3mp8-cgmx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-47737</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-47737</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: puma, Ubuntu:24.04:LTS: puma, Ubuntu:26.04:LTS: puma&lt;/p&gt;
&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: puma, Ubuntu:24.04:LTS: puma, Ubuntu:26.04:LTS: puma&lt;/p&gt;
&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-47737</guid>
    </item>
  </channel>
</rss>
