🛡️ CLSA-2026-1769511237 — ruby
Description
ruby: Fix of 2 CVEs
- CVE-2025-61594: fix incomplete fix for CVE-2025-27221 which allowed credential leaks
to persist in URI#+
CVE-2025-27221: fix credential leak by correctly truncating userinfo
Affected software
CLSA-2026-1769511237 is recorded against 22 packages.
- ruby (fixed in 3.0.4-160.el9_0.tuxcare.els11)
- ruby-default-gems (fixed in 3.0.4-160.el9_0.tuxcare.els11)
- ruby-devel (fixed in 3.0.4-160.el9_0.tuxcare.els11)
- ruby-doc (fixed in 3.0.4-160.el9_0.tuxcare.els11)
- ruby-libs (fixed in 3.0.4-160.el9_0.tuxcare.els11)
- rubygem-bigdecimal (fixed in 3.0.0-160.el9_0.tuxcare.els11)
- rubygem-bundler (fixed in 2.2.33-160.el9_0.tuxcare.els11)
- rubygem-io-console (fixed in 0.5.7-160.el9_0.tuxcare.els11)
- rubygem-irb (fixed in 1.3.5-160.el9_0.tuxcare.els11)
- rubygem-json (fixed in 2.5.1-160.el9_0.tuxcare.els11)
- rubygem-minitest (fixed in 5.14.2-160.el9_0.tuxcare.els11)
- rubygem-power-assert (fixed in 1.2.0-160.el9_0.tuxcare.els11)
- rubygem-psych (fixed in 3.3.2-160.el9_0.tuxcare.els11)
- rubygem-rake (fixed in 13.0.3-160.el9_0.tuxcare.els11)
- rubygem-rbs (fixed in 1.4.0-160.el9_0.tuxcare.els11)
- rubygem-rdoc (fixed in 6.3.3-160.el9_0.tuxcare.els11)
- rubygem-rexml (fixed in 3.3.3-160.el9_0.tuxcare.els11)
- rubygem-rss (fixed in 0.2.9-160.el9_0.tuxcare.els11)
- rubygem-test-unit (fixed in 3.3.7-160.el9_0.tuxcare.els11)
- rubygem-typeprof (fixed in 0.15.2-160.el9_0.tuxcare.els11)
- rubygems (fixed in 3.2.33-160.el9_0.tuxcare.els11)
- rubygems-devel (fixed in 3.2.33-160.el9_0.tuxcare.els11)
Timeline and source
Published on 27 January 2026 and last revised on 1 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| ruby | — | 3.0.4-160.el9_0.tuxcare.els11 |
| ruby-default-gems | — | 3.0.4-160.el9_0.tuxcare.els11 |
| ruby-devel | — | 3.0.4-160.el9_0.tuxcare.els11 |
| ruby-doc | — | 3.0.4-160.el9_0.tuxcare.els11 |
| ruby-libs | — | 3.0.4-160.el9_0.tuxcare.els11 |
| rubygem-bigdecimal | — | 3.0.0-160.el9_0.tuxcare.els11 |
| rubygem-bundler | — | 2.2.33-160.el9_0.tuxcare.els11 |
| rubygem-io-console | — | 0.5.7-160.el9_0.tuxcare.els11 |
| rubygem-irb | — | 1.3.5-160.el9_0.tuxcare.els11 |
| rubygem-json | — | 2.5.1-160.el9_0.tuxcare.els11 |
| rubygem-minitest | — | 5.14.2-160.el9_0.tuxcare.els11 |
| rubygem-power-assert | — | 1.2.0-160.el9_0.tuxcare.els11 |
| rubygem-psych | — | 3.3.2-160.el9_0.tuxcare.els11 |
| rubygem-rake | — | 13.0.3-160.el9_0.tuxcare.els11 |
| rubygem-rbs | — | 1.4.0-160.el9_0.tuxcare.els11 |
| rubygem-rdoc | — | 6.3.3-160.el9_0.tuxcare.els11 |
| rubygem-rexml | — | 3.3.3-160.el9_0.tuxcare.els11 |
| rubygem-rss | — | 0.2.9-160.el9_0.tuxcare.els11 |
| rubygem-test-unit | — | 3.3.7-160.el9_0.tuxcare.els11 |
| rubygem-typeprof | — | 0.15.2-160.el9_0.tuxcare.els11 |
| rubygems | — | 3.2.33-160.el9_0.tuxcare.els11 |
| rubygems-devel | — | 3.2.33-160.el9_0.tuxcare.els11 |
References
Similar Threats
- Unknown ALPINE-CVE-2026-27820
- Unknown ALPINE-CVE-2025-61594
- Unknown ALPINE-CVE-2025-27219
- Unknown ALPINE-CVE-2024-27280
- Unknown ALPINE-CVE-2024-27281
More CLSA 2026 advisories
Browse all of CLSA 2026 in the advisory index.
- CLSA-2026-1769506798
- CLSA-2026-1769507433
- CLSA-2026-1769507695
- CLSA-2026-1769507907
- CLSA-2026-1769508535
- CLSA-2026-1769509482
- CLSA-2026-1769510148
- CLSA-2026-1769510460
- CLSA-2026-1769513855
- CLSA-2026-1769515411
- CLSA-2026-1769516003
- CLSA-2026-1769516785
- CLSA-2026-1769524269
- CLSA-2026-1769542154
- CLSA-2026-1769559170
- CLSA-2026-1769559191
Free Vulnerability Check
Is your site affected by CLSA-2026-1769511237?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CLSA-2026-1769511237 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.