<?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>Tue, 06 Oct 2026 07:04:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-23634 — Information Exposure when using Puma with Rails</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-23634</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; puma&lt;/p&gt;
&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails&amp;#39; Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; puma&lt;/p&gt;
&lt;p&gt;Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails&amp;#39; Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-23634</guid>
    </item>
    <item>
      <title>GHSA-rmj8-8hhh-gv5h — Puma used with Rails may lead to Information Exposure</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rmj8-8hhh-gv5h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: puma&lt;/p&gt;
&lt;p&gt;### Impact
Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly.&lt;/p&gt;
&lt;p&gt;From Rails:&lt;/p&gt;
&lt;p&gt;&amp;gt; Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.&lt;/p&gt;
&lt;p&gt;The combination of these two behaviors (Puma not closing the body + Rails&amp;#39; Executor implementation) causes information leakage.&lt;/p&gt;
&lt;p&gt;### Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.&lt;/p&gt;
&lt;p&gt;This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.&lt;/p&gt;
&lt;p&gt;See: 
https://github.com/advisories/GHSA-wh98-p28r-vrc9 
for details about the rails vulnerability&lt;/p&gt;
&lt;p&gt;Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.&lt;/p&gt;
&lt;p&gt;The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&amp;amp;utm_source=footer&amp;amp;pli=1) includes a middleware that can be used instead.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Rails CVE: [CVE-2022-23633](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlB…&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
Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly.&lt;/p&gt;
&lt;p&gt;From Rails:&lt;/p&gt;
&lt;p&gt;&amp;gt; Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.&lt;/p&gt;
&lt;p&gt;The combination of these two behaviors (Puma not closing the body + Rails&amp;#39; Executor implementation) causes information leakage.&lt;/p&gt;
&lt;p&gt;### Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.&lt;/p&gt;
&lt;p&gt;This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.&lt;/p&gt;
&lt;p&gt;See: 
https://github.com/advisories/GHSA-wh98-p28r-vrc9 
for details about the rails vulnerability&lt;/p&gt;
&lt;p&gt;Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.&lt;/p&gt;
&lt;p&gt;The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&amp;amp;utm_source=footer&amp;amp;pli=1) includes a middleware that can be used instead.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Rails CVE: [CVE-2022-23633](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlB…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rmj8-8hhh-gv5h</guid>
    </item>
  </channel>
</rss>
