CVE-2026-46727: Jruby · An issue was discovered in Ruby 4 before 4.0.5
Affects jrubySource GCVE Database
Not known to be exploited · CVSS 8.1 High · fixed in 4.0.5 : patch jruby soon.
Data as of 17 Nov 2026, 20:40 UTC
- Patch
- Available – fixed in 4.0.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 May 2026
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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10jrubypkg:deb/ubuntu/jruby?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10ruby3.3pkg:deb/ubuntu/ruby3.3?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSruby3.3pkg:deb/ubuntu/ruby3.3?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10jrubypkg:deb/ubuntu/jruby?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10ruby3.3pkg:deb/ubuntu/ruby3.3?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSruby3.2pkg:deb/ubuntu/ruby3.2?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Ruby version 4.0.5. Users should upgrade to Ruby 4.0.5 or later to remediate this vulnerability. No additional mitigation steps are indicated in the provided data.
Description
A race condition vulnerability in Ruby 4 versions prior to 4.0.5 allows a remote attacker to cause a use-after-free in the pthread-based getaddrinfo timeout handler. This can lead to a crash of the Ruby process when calling Addrinfo.getaddrinfo or Socket.tcp with timeout parameters. Exploitation could be triggered by delaying DNS responses, potentially via a malicious DNS server or resolver. Memory corruption exploitation is theoretically possible.