<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ruby-Lang on CVE Alert &amp; Security Feed</title><link>https://cvealert.net/vendors/ruby-lang/</link><description>Recent content in Ruby-Lang on CVE Alert &amp; Security Feed</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 18:16:22 +0000</lastBuildDate><atom:link href="https://cvealert.net/vendors/ruby-lang/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-46727</title><link>https://cvealert.net/posts/cve-2026-46727/</link><pubDate>Fri, 22 May 2026 18:16:22 +0000</pubDate><guid>https://cvealert.net/posts/cve-2026-46727/</guid><description>An issue was discovered in Ruby 4 before 4.0.5. A race condition leading to a use-after-free in the pthread-based getaddrinfo timeout handler (rb_getaddrinfo in ext/socket/raddrinfo.c) allows a remote attacker who can delay DNS responses near the user-specified timeout to crash a Ruby process that calls Addrinfo.getaddrinfo(&amp;hellip;, timeout:) or Socket.tcp(&amp;hellip;, resolv_timeout:). Memory-corruption-based exploitation is theoretically possible. The attack could, for example, be carried out through a crafted authoritative DNS server or recursive resolver.</description></item></channel></rss>