SUSE · Security update for rubygem-rack
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · fixed in SUSE package updates : patch SUSE soon.
Data as of 15 Nov 2026, 23:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- Patch
- Available – fixed in 2.2.20
Exploitation evidence
Disclosed: evidence found.
CVE published 27 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
AI-suggested
Apply the security update by upgrading rubygem-rack to version 2.2.20, which contains fixes for both CVE-2025-61919 and CVE-2025-61780. No additional mitigation steps are indicated.
Description
This security update for rubygem-rack addresses two vulnerabilities: CVE-2025-61919, which fixes an issue with calling rack.input.read(nil) without enforcing a length or cap in application/x-www-form-urlencoded requests, and CVE-2025-61780, which fixes improper handling of headers in Rack::Sendfile that could allow bypass of proxy-level access restrictions. The update is included in version 2.2.20.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_4273-1.json (opens in a new tab)
- suse.com/support/update/announcement/2025/suse-su-20254273-1/ (opens in a new tab)
- lists.suse.com/pipermail/sle-security-updates/2025-November/023401.html (opens in a new tab)
- bugzilla.suse.com/1251936 (opens in a new tab)
- bugzilla.suse.com/1253951 (opens in a new tab)
- suse.com/security/cve/CVE-2025-61780/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-61919/ (opens in a new tab)