<?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:22:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07772</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07772</link>
      <description>bdu:2024-07772</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07772</guid>
    </item>
    <item>
      <title>EUVD-2026-241350</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-241350</link>
      <description>EUVD-2026-241350</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-241350</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41136</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41136</link>
      <description>&lt;p&gt;Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41136</guid>
    </item>
    <item>
      <title>GHSA-48w2-rm65-62xx — Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-48w2-rm65-62xx</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;Prior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.&lt;/p&gt;
&lt;p&gt;This behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as &amp;#34;low&amp;#34;. Puma is only aware of a single proxy server which has this behavior.&lt;/p&gt;
&lt;p&gt;If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This vulnerability was patched in Puma 5.5.1 and 4.3.9.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;This vulnerability only affects Puma installations without any proxy in front.&lt;/p&gt;
&lt;p&gt;Use a proxy which does not forward LF characters as line endings.&lt;/p&gt;
&lt;p&gt;Proxies which do not forward LF characters as line endings:&lt;/p&gt;
&lt;p&gt;* Nginx
* Apache (&amp;gt;2.4.25)
* Haproxy
* Caddy
* Traefik&lt;/p&gt;
&lt;p&gt;### Possible Breakage&lt;/p&gt;
&lt;p&gt;If you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-…&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;Prior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.&lt;/p&gt;
&lt;p&gt;This behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as &amp;#34;low&amp;#34;. Puma is only aware of a single proxy server which has this behavior.&lt;/p&gt;
&lt;p&gt;If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This vulnerability was patched in Puma 5.5.1 and 4.3.9.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;This vulnerability only affects Puma installations without any proxy in front.&lt;/p&gt;
&lt;p&gt;Use a proxy which does not forward LF characters as line endings.&lt;/p&gt;
&lt;p&gt;Proxies which do not forward LF characters as line endings:&lt;/p&gt;
&lt;p&gt;* Nginx
* Apache (&amp;gt;2.4.25)
* Haproxy
* Caddy
* Traefik&lt;/p&gt;
&lt;p&gt;### Possible Breakage&lt;/p&gt;
&lt;p&gt;If you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-48w2-rm65-62xx</guid>
    </item>
    <item>
      <title>gsd-2021-41136</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41136</link>
      <description>gsd-2021-41136</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41136</guid>
    </item>
    <item>
      <title>OESA-2023-1981 — rubygem-puma security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2023-1981</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: 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 HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;amp;apos;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.(CVE-2021-41136)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: 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 HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;amp;apos;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.(CVE-2021-41136)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2023-1981</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:11830-1 — ruby3.1-rubygem-puma-4-4.3.10-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:11830-1</link>
      <description>&lt;p&gt;ruby3.1-rubygem-puma-4-4.3.10-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ruby3.1-rubygem-puma-4-4.3.10-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:11830-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-2021:3728-1 — Security update for ardana-ansible, ardana-monasca, documentation-suse-openstack-cloud, openstack-ec2-api, openstack-he…</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2021:3728-1</link>
      <description>&lt;p&gt;Security update for ardana-ansible, ardana-monasca, documentation-suse-openstack-cloud, openstack-ec2-api, openstack-heat-templates, python-Django, python-monasca-common, rubygem-redcarpet, rubygem-puma&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for ardana-ansible, ardana-monasca, documentation-suse-openstack-cloud, openstack-ec2-api, openstack-heat-templates, python-Django, python-monasca-common, rubygem-redcarpet, rubygem-puma&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2021:3728-1</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2021-41136</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41136</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: puma, Ubuntu:22.04:LTS: puma&lt;/p&gt;
&lt;p&gt;Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: puma, Ubuntu:22.04:LTS: puma&lt;/p&gt;
&lt;p&gt;Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request&amp;#39;s body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41136</guid>
    </item>
  </channel>
</rss>
