<?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 19:46:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07773</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07773</link>
      <description>bdu:2024-07773</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07773</guid>
    </item>
    <item>
      <title>cnvd-2022-10705</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-10705</link>
      <description>cnvd-2022-10705</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-10705</guid>
    </item>
    <item>
      <title>EUVD-2026-234452</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-234452</link>
      <description>EUVD-2026-234452</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-234452</guid>
    </item>
    <item>
      <title>fkie_cve-2022-23634</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-23634</link>
      <description>&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;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/fkie_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>
    <item>
      <title>gsd-2022-23634</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-23634</link>
      <description>gsd-2022-23634</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-23634</guid>
    </item>
    <item>
      <title>OESA-2024-1002 — rubygem-puma security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP2: rubygem-puma&lt;/p&gt;
&lt;p&gt;A simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications.&#13;
&#13;
Security Fix(es):&#13;
&#13;
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;amp;apos; 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.(CVE-2022-23634)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP2: rubygem-puma&lt;/p&gt;
&lt;p&gt;A simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications.&#13;
&#13;
Security Fix(es):&#13;
&#13;
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;amp;apos; 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.(CVE-2022-23634)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1002</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:11847-1 — ruby3.1-rubygem-puma-5.6.2-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:11847-1</link>
      <description>&lt;p&gt;ruby3.1-rubygem-puma-5.6.2-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ruby3.1-rubygem-puma-5.6.2-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:11847-1</guid>
    </item>
    <item>
      <title>RHSA-2022:5498 — Red Hat Security Advisory: Satellite 6.11 Release</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:5498</link>
      <description>&lt;p&gt;libsolv: heap-based buffer overflow in testcase_read() in src/testcase.c foreman: Authenticate remote code execution through Sendmail configuration Satellite: Allow unintended SCA certificate to authenticate Candlepin netty: Information disclosure via the local system temporary directory netty: possible request smuggling in HTTP/2 due missing validation netty: Request smuggling via content-length header sidekiq: XSS via the queue name of the live-poll feature python-sqlparse: ReDoS via regular expression in StripComments filter libsolv: heap-based buffer overflow in pool_installable() in src/repo.h libsolv: heap-based buffer overflow in pool_disabled_solvable() in src/repo.h libsolv: heap-based buffer overflow in pool_installable_whatprovides() in src/repo.h libsolv: heap-based buffer overflow in prune_to_recommended() in src/policy.c rubygem-puma: Inconsistent Interpretation of HTTP Requests (&amp;#39;HTTP Request Smuggling&amp;#39;) in puma logback: remote code execution through JNDI call from within its configuration file netty: control chars in header names may lead to HTTP request smuggling python-lxml: HTML Cleaner allows crafted and SVG embedded scripts to pass through django: potential bypass of an upstream access control based on URL paths libsolv: heap-overflows in resolve_dependencies function django: Denial-of-service possibility in UserAttributeSimilarityValidator django: Potential information disclosure in dictsort template filter django: Potential directory-traversal via Stor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libsolv: heap-based buffer overflow in testcase_read() in src/testcase.c foreman: Authenticate remote code execution through Sendmail configuration Satellite: Allow unintended SCA certificate to authenticate Candlepin netty: Information disclosure via the local system temporary directory netty: possible request smuggling in HTTP/2 due missing validation netty: Request smuggling via content-length header sidekiq: XSS via the queue name of the live-poll feature python-sqlparse: ReDoS via regular expression in StripComments filter libsolv: heap-based buffer overflow in pool_installable() in src/repo.h libsolv: heap-based buffer overflow in pool_disabled_solvable() in src/repo.h libsolv: heap-based buffer overflow in pool_installable_whatprovides() in src/repo.h libsolv: heap-based buffer overflow in prune_to_recommended() in src/policy.c rubygem-puma: Inconsistent Interpretation of HTTP Requests (&amp;#39;HTTP Request Smuggling&amp;#39;) in puma logback: remote code execution through JNDI call from within its configuration file netty: control chars in header names may lead to HTTP request smuggling python-lxml: HTML Cleaner allows crafted and SVG embedded scripts to pass through django: potential bypass of an upstream access control based on URL paths libsolv: heap-overflows in resolve_dependencies function django: Denial-of-service possibility in UserAttributeSimilarityValidator django: Potential information disclosure in dictsort template filter django: Potential directory-traversal via Stor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:5498</guid>
    </item>
    <item>
      <title>SUSE-SU-2022:1515-1 — Security update for rubygem-puma</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2022:1515-1</link>
      <description>&lt;p&gt;Security update for rubygem-puma&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for rubygem-puma&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2022:1515-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-23634</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-23634</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: 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; Ubuntu:Pro:20.04:LTS: puma, Ubuntu:Pro:22.04:LTS: 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/ubuntu-cve-2022-23634</guid>
    </item>
  </channel>
</rss>
