https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:52:23 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-07732 bdu:2026-07732 https://cve.radiocsirt.org/vuln/bdu:2026-07732 https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-34826 <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>`Rack::Utils.get_byte_ranges` parses the HTTP `Range` header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as `0-0,0-0,0-0,...` to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request.</p> <p>This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses.</p> <p>## Details</p> <p>`Rack::Utils.get_byte_ranges` accepts a comma-separated list of byte ranges and validates them based on their aggregate size, but does not impose a limit on how many individual ranges may be supplied.</p> <p>As a result, a request such as:</p> <p>```http Range: bytes=0-0,0-0,0-0,0-0,... ```</p> <p>can contain thousands of overlapping one-byte ranges while still satisfying the total-size check added for CVE-2024-26141.</p> <p>When such a header is processed by Rack’s file-serving code, each range causes additional work, including multipart response generation, per-range iteration, file seek and read operations, and temporary string allocation for response size calculation and output. This allows a relatively small request header to trigger disproportionately expensive processing and a much larger multipart response.</p> <p>The issue is distinct from CVE-2024-26141. That fix prevents range sets whose total byte coverage exceeds the file size,…</p> <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>`Rack::Utils.get_byte_ranges` parses the HTTP `Range` header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as `0-0,0-0,0-0,...` to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request.</p> <p>This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses.</p> <p>## Details</p> <p>`Rack::Utils.get_byte_ranges` accepts a comma-separated list of byte ranges and validates them based on their aggregate size, but does not impose a limit on how many individual ranges may be supplied.</p> <p>As a result, a request such as:</p> <p>```http Range: bytes=0-0,0-0,0-0,0-0,... ```</p> <p>can contain thousands of overlapping one-byte ranges while still satisfying the total-size check added for CVE-2024-26141.</p> <p>When such a header is processed by Rack’s file-serving code, each range causes additional work, including multipart response generation, per-range iteration, file seek and read operations, and temporary string allocation for response size calculation and output. This allows a relatively small request header to trigger disproportionately expensive processing and a much larger multipart response.</p> <p>The issue is distinct from CVE-2024-26141. That fix prevents range sets whose total byte coverage exceeds the file size,…</p> https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-34826 https://cve.radiocsirt.org/vuln/euvd-2026-280215 EUVD-2026-280215 https://cve.radiocsirt.org/vuln/euvd-2026-280215 https://cve.radiocsirt.org/vuln/fkie_cve-2026-34826 <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.get_byte_ranges parses the HTTP Range header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as 0-0,0-0,0-0,... to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request. This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.get_byte_ranges parses the HTTP Range header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as 0-0,0-0,0-0,... to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request. This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-34826 https://cve.radiocsirt.org/vuln/ghsa-x8cg-fq8g-mxfx <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>`Rack::Utils.get_byte_ranges` parses the HTTP `Range` header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as `0-0,0-0,0-0,...` to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request.</p> <p>This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses.</p> <p>## Details</p> <p>`Rack::Utils.get_byte_ranges` accepts a comma-separated list of byte ranges and validates them based on their aggregate size, but does not impose a limit on how many individual ranges may be supplied.</p> <p>As a result, a request such as:</p> <p>```http Range: bytes=0-0,0-0,0-0,0-0,... ```</p> <p>can contain thousands of overlapping one-byte ranges while still satisfying the total-size check added for CVE-2024-26141.</p> <p>When such a header is processed by Rack’s file-serving code, each range causes additional work, including multipart response generation, per-range iteration, file seek and read operations, and temporary string allocation for response size calculation and output. This allows a relatively small request header to trigger disproportionately expensive processing and a much larger multipart response.</p> <p>The issue is distinct from CVE-2024-26141. That fix prevents range sets whose total byte coverage exceeds the file size,…</p> <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>`Rack::Utils.get_byte_ranges` parses the HTTP `Range` header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as `0-0,0-0,0-0,...` to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request.</p> <p>This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses.</p> <p>## Details</p> <p>`Rack::Utils.get_byte_ranges` accepts a comma-separated list of byte ranges and validates them based on their aggregate size, but does not impose a limit on how many individual ranges may be supplied.</p> <p>As a result, a request such as:</p> <p>```http Range: bytes=0-0,0-0,0-0,0-0,... ```</p> <p>can contain thousands of overlapping one-byte ranges while still satisfying the total-size check added for CVE-2024-26141.</p> <p>When such a header is processed by Rack’s file-serving code, each range causes additional work, including multipart response generation, per-range iteration, file seek and read operations, and temporary string allocation for response size calculation and output. This allows a relatively small request header to trigger disproportionately expensive processing and a much larger multipart response.</p> <p>The issue is distinct from CVE-2024-26141. That fix prevents range sets whose total byte coverage exceeds the file size,…</p> https://cve.radiocsirt.org/vuln/ghsa-x8cg-fq8g-mxfx https://cve.radiocsirt.org/vuln/opensuse-su-2026:10508-1 <p>ruby4.0-rubygem-rack-2.2-2.2.23-1.1 on GA media</p> <p>ruby4.0-rubygem-rack-2.2-2.2.23-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10508-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23321-1 <p>Security update for rmt-server</p> <p>Security update for rmt-server</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23321-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34826 <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:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack, Ubuntu:25.10: ruby-rack, Ubuntu:26.04:LTS: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.get_byte_ranges parses the HTTP Range header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as 0-0,0-0,0-0,... to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request. This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.</p> <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:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack, Ubuntu:25.10: ruby-rack, Ubuntu:26.04:LTS: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.get_byte_ranges parses the HTTP Range header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as 0-0,0-0,0-0,... to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request. This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34826 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1687 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1687