<?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://127.0.0.1:10001</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, 21 Nov 2026 00:44:19 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:19719 — Important: pcs security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2025:19719</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: pcs, AlmaLinux:8: pcs-snmp&lt;/p&gt;
&lt;p&gt;The pcs packages provide a command-line configuration system for the Pacemaker and Corosync utilities.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters (CVE-2025-59830)
  * rack: Rack&amp;#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) (CVE-2025-61770)
  * rack: Rack&amp;#39;s multipart parser buffers large non?file fields entirely in memory, enabling DoS (memory exhaustion) (CVE-2025-61771)
  * rack: Rack memory exhaustion denial of service (CVE-2025-61772)
  * rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion (CVE-2025-61919)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: pcs, AlmaLinux:8: pcs-snmp&lt;/p&gt;
&lt;p&gt;The pcs packages provide a command-line configuration system for the Pacemaker and Corosync utilities.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters (CVE-2025-59830)
  * rack: Rack&amp;#39;s unbounded multipart preamble buffering enables DoS (memory exhaustion) (CVE-2025-61770)
  * rack: Rack&amp;#39;s multipart parser buffers large non?file fields entirely in memory, enabling DoS (memory exhaustion) (CVE-2025-61771)
  * rack: Rack memory exhaustion denial of service (CVE-2025-61772)
  * rubygem-rack: Unbounded read in `Rack::Request` form parsing can lead to memory exhaustion (CVE-2025-61919)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2025:19719</guid>
    </item>
    <item>
      <title>BREW-mailcatcher-CVE-2025-59830 — Rack has an unsafe default in Rack::QueryParser allows params_limit bypass via semicolon-separated parameters</title>
      <link>https://127.0.0.1:10001/vuln/brew-mailcatcher-cve-2025-59830</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::QueryParser` in version `&amp;lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;amp;`, while still splitting on both `&amp;amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;amp;;] */n` splits on both `&amp;amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.&lt;/p&gt;
&lt;p&gt;Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.&lt;/p&gt;
&lt;p&gt;`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of Rack where both `&amp;amp;` and `;` are counted consistently toward `params_limit`.
* If upgrading is not immediately possible, configure `QueryParser` with an…&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::QueryParser` in version `&amp;lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;amp;`, while still splitting on both `&amp;amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;amp;;] */n` splits on both `&amp;amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.&lt;/p&gt;
&lt;p&gt;Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Applications or middleware that directly invoke `Rack::QueryParser` with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector.&lt;/p&gt;
&lt;p&gt;`Rack::Request`, the primary entry point for typical Rack applications, uses `QueryParser` in a safe way and does not appear vulnerable by default. As such, the severity is considered **low**, with the impact limited to edge cases where `QueryParser` is used directly.&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched version of Rack where both `&amp;amp;` and `;` are counted consistently toward `params_limit`.
* If upgrading is not immediately possible, configure `QueryParser` with an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-mailcatcher-cve-2025-59830</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0967 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0967</link>
      <description>certfr-2025-avi-0967</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0967</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-59830</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-59830</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:20.04:LTS: ruby-rack, Ubuntu:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;amp;, while still splitting on both &amp;amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.&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:20.04:LTS: ruby-rack, Ubuntu:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &amp;amp;, while still splitting on both &amp;amp; and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-59830</guid>
    </item>
  </channel>
</rss>
