Linux · 
openSUSE Leap · Security advisory · September 18, 2026
openSUSE Leap · Security advisory · September 18, 2026OPENSUSE-SU-2026:21878-1: ruby3.4 security update
OPENSUSE-SU-2026:21878-1, released September 18, 2026, fixes 8 CVEs in ruby3.4 (version 3.4.10-160000.1.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0113
66th percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 8
Routine 0
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| ruby3.4 | opensuse-leap 16.0 | 3.4.10-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-41316 | ruby2.5: erb: @_init deserialization guard bypass via def_module / def_method / def_class (bsc#1262441). | 9.1 | 0.0113 | None reported |
| High | CVE-2026-47240 | Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument | 7.3 | 0.0083 | None reported |
| High | CVE-2026-42258 | net-imap: Command Injection via unvalidated Symbol inputs | 7.4 | 0.0078 | None reported |
| High | CVE-2026-27820 | zlib: Buffer Overflow in Zlib::GzipReader ungetc via large input leads to memory corruption | 9.8 | 0.0056 | None reported |
| High | CVE-2025-61594 | ruby3.4: merging URIs using the + operator could expose sensitive user credentials (bsc#1270034). | 7.5 | 0.0056 | None reported |
| High | CVE-2026-47241 | Net::IMAP: Denial of Service via incomplete raw argument validation | 7.3 | 0.0038 | None reported |
| High | CVE-2025-58767 | REXML has a DoS condition when parsing malformed XML file | 7.5 | 0.0025 | None reported |
| High | CVE-2026-47242 | ruby: Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby | 7.3 | 0.0018 | None reported |
Showing 1 to 8 of 8
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.