https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 19:44:14 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13873 bdu:2025-13873 https://cve.radiocsirt.org/vuln/bdu:2025-13873 https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-61780 <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>A possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions.</p> <p>## Details</p> <p>When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was **not subject to the proxy&#39;s access controls**.</p> <p>An attacker could exploit this by: 1. Setting a crafted `x-sendfile-type: x-accel-redirect` header. 2. Setting a crafted `x-accel-mapping` header. 3. Requesting a path that qualifies for proxy-based acceleration.</p> <p>## Impact</p> <p>Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes.</p> <p>This issue only affected systems meeting all of the following conditions:</p> <p>* The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx). * The proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers. * The application exposed an endpoint that returned…</p> <p><strong>Affected:</strong> Homebrew: mailcatcher</p> <p>## Summary</p> <p>A possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions.</p> <p>## Details</p> <p>When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was **not subject to the proxy&#39;s access controls**.</p> <p>An attacker could exploit this by: 1. Setting a crafted `x-sendfile-type: x-accel-redirect` header. 2. Setting a crafted `x-accel-mapping` header. 3. Requesting a path that qualifies for proxy-based acceleration.</p> <p>## Impact</p> <p>Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes.</p> <p>This issue only affected systems meeting all of the following conditions:</p> <p>* The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx). * The proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers. * The application exposed an endpoint that returned…</p> https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2025-61780 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0967 https://cve.radiocsirt.org/vuln/cleanstart-2026-ho19975 <p><strong>Affected:</strong> CleanStart: logstash-fips</p> <p>CVE-2025-61780 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: logstash-fips</p> <p>CVE-2025-61780 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-ho19975 https://cve.radiocsirt.org/vuln/euvd-2026-254693 EUVD-2026-254693 https://cve.radiocsirt.org/vuln/euvd-2026-254693 https://cve.radiocsirt.org/vuln/fkie_cve-2025-61780 <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy&#39;s access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the applicat…</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy&#39;s access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the applicat…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-61780 https://cve.radiocsirt.org/vuln/ghsa-r657-rxjc-j557 <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>A possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions.</p> <p>## Details</p> <p>When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was **not subject to the proxy&#39;s access controls**.</p> <p>An attacker could exploit this by: 1. Setting a crafted `x-sendfile-type: x-accel-redirect` header. 2. Setting a crafted `x-accel-mapping` header. 3. Requesting a path that qualifies for proxy-based acceleration.</p> <p>## Impact</p> <p>Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes.</p> <p>This issue only affected systems meeting all of the following conditions:</p> <p>* The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx). * The proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers. * The application exposed an endpoint that returned…</p> <p><strong>Affected:</strong> RubyGems: rack</p> <p>## Summary</p> <p>A possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions.</p> <p>## Details</p> <p>When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was **not subject to the proxy&#39;s access controls**.</p> <p>An attacker could exploit this by: 1. Setting a crafted `x-sendfile-type: x-accel-redirect` header. 2. Setting a crafted `x-accel-mapping` header. 3. Requesting a path that qualifies for proxy-based acceleration.</p> <p>## Impact</p> <p>Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes.</p> <p>This issue only affected systems meeting all of the following conditions:</p> <p>* The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx). * The proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers. * The application exposed an endpoint that returned…</p> https://cve.radiocsirt.org/vuln/ghsa-r657-rxjc-j557 https://cve.radiocsirt.org/vuln/suse-su-2025:4273-1 <p>Security update for rubygem-rack</p> <p>Security update for rubygem-rack</p> https://cve.radiocsirt.org/vuln/suse-su-2025:4273-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-61780 <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, Ubuntu:25.10: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy&#39;s access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the applicat…</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:20.04:LTS: ruby-rack, Ubuntu:22.04:LTS: ruby-rack, Ubuntu:24.04:LTS: ruby-rack, Ubuntu:25.10: ruby-rack</p> <p>Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a &#34;redirect&#34; response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy&#39;s access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the applicat…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-61780