<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T00:44:22.137902+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/alsa-2025:19719</id>
    <title>ALSA-2025:19719 — Important: pcs security update</title>
    <updated>2026-11-21T00:44:22.146872+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: pcs, AlmaLinux:8: pcs-snmp</p>
<p>The pcs packages provide a command-line configuration system for the Pacemaker and Corosync utilities.</p>
<p>Security Fix(es):</p>
<p>* rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters (CVE-2025-59830)
  * rack: Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion) (CVE-2025-61770)
  * rack: Rack'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)</p>
<p>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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2025:19719"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/brew-mailcatcher-cve-2025-59830</id>
    <title>BREW-mailcatcher-CVE-2025-59830 — Rack has an unsafe default in Rack::QueryParser allows params_limit bypass via semicolon-separated parameters</title>
    <updated>2026-11-21T00:44:22.146975+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: mailcatcher</p>
<p>## Summary</p>
<p>`Rack::QueryParser` in version `&lt; 2.2.18` enforces its `params_limit` only for parameters separated by `&amp;`, while still splitting on both `&amp;` and `;`. As a result, attackers could use `;` separators to bypass the parameter count limit and submit more parameters than intended.</p>
<p>## Details</p>
<p>The issue arises because `Rack::QueryParser#check_query_string` counts only `&amp;` characters when determining the number of parameters, but the default separator regex `DEFAULT_SEP = /[&amp;;] */n` splits on both `&amp;` and `;`. This mismatch means that queries using `;` separators were not included in the parameter count, allowing `params_limit` to be bypassed.</p>
<p>Other safeguards (`bytesize_limit` and `key_space_limit`) still applied, but did not prevent this particular bypass.</p>
<p>## Impact</p>
<p>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.</p>
<p>`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.</p>
<p>## Mitigation</p>
<p>* Upgrade to a patched version of Rack where both `&amp;` and `;` are counted consistently toward `params_limit`.
* If upgrading is not immediately possible, configure `QueryParser` with an…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/brew-mailcatcher-cve-2025-59830"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0967</id>
    <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>
    <updated>2026-11-21T00:44:22.147036+00:00</updated>
    <content>certfr-2025-avi-0967</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0967"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-59830</id>
    <title>UBUNTU-CVE-2025-59830</title>
    <updated>2026-11-21T00:44:22.147056+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;, while still splitting on both &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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-59830"/>
  </entry>
</feed>
