{"slug": "a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before", "title": "A Botnet Started Exploiting a Critical Ray Flaw Two Days Before", "summary": "The RondoDox botnet began exploiting CVE-2025-62593 in Ray, a framework used by Amazon, Apple, and OpenAI to scale machine learning, on November 24, 2025, two days before the CVE was published, according to Bitsight. The flaw, with a CVSS 4.0 score of 9.4, affects all Ray versions before 2.52.0 and allows code execution via DNS rebinding without authentication. CISA added it to its Known Exploited Vulnerabilities catalog on August 17, 2026, with a federal remediation deadline of August 20.", "body_md": "# A Botnet Started Exploiting a Critical Ray Flaw Two Days Before\n\nCVE-2025-62593 in Ray, the framework Amazon, Apple and OpenAI use to scale ML, was exploited by the RondoDox botnet two days before the CVE was even…\n\nUsually the timeline for a critical vulnerability goes: flaw discovered, CVE published, attackers start exploiting. CVE-2025-62593 in Ray broke that order in a way you should sit with.\n\nBitsight reported that the RondoDox botnet began attempting to exploit the flaw on November 24, 2025, two full days before the CVE was published. The operators weren't waiting for a formal advisory. They were tracking public vulnerability research in real time, and they beat the disclosure to the punch.\n\n## The Flaw Itself\n\nRay is the Python-native framework for scaling AI and ML workloads, sitting at over 43,500 GitHub stars, used by Amazon, Apple and [OpenAI](/glossary/openai). The vulnerability carries a CVSS 4.0 score of 9.4 and affects every version before 2.52.0. CISA moved it to its Known Exploited Vulnerabilities catalog on August 17, upgrading it from proof-of-concept to active exploitation.\n\nWhat makes it different from most critical CVEs is the target. This isn't a server you patch in a data centre. The attack path runs through a browser: a developer visits a malicious page, or even just sees a malicious advert in Firefox or Safari, while Ray runs locally, and gets code execution against that local instance via DNS rebinding. No login required.\n\n## The Root Cause Is a Decision\n\nRay's own maintainers were blunt about why this happened. It's a longstanding decision not to implement authentication on critical endpoints. That's not a bug in the usual sense. It's a design choice that assumed Ray would always live behind a trusted network boundary, and it's the kind of assumption that holds right up until the moment it doesn't.\n\nThe practical problem is worse than the diagnosis. Ray doesn't just run on laptops. It sits inside CI runners, container base images and Kubernetes workloads where nobody thinks to look for it. The federal remediation deadline of August 20 binds agencies. Everyone else patches or doesn't, and the botnet operators have had a nine-month head start.\n\n## The Part That Should Bother You\n\nThe timeline is the story, because it changes what security teams should assume. If operators are now exploiting vulnerabilities two days before the CVE drops, then the CVE is not your early warning. It's your confirmation that you're already late.\n\nThat means the only real defense is fixing the fundamentals: authenticate your endpoints, don't expose local services to browsers, and treat research previews and vendor advisories as trailing indicators rather than alarm bells. The botnet that beat the disclosure by two days is not going to be the last one that reads the research before you do.\n\nHere's the hard question worth asking this week: how many Ray installations inside your organisation are still below 2.52.0, and who knows where they all are? Because if the answer is \"we're not sure,\" the RondoDox operators may already know better than you do.\n\n*Sources: CISA Known Exploited Vulnerabilities catalog entry CVE-2025-62593, August 17, 2026; Bitsight RondoDox botnet reporting, August 2026; AI Tools Recap daily briefing, August 22, 2026.*\n\nGet AI news in your inbox\n\nDaily digest of what matters in AI.", "url": "https://wpnews.pro/news/a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before", "canonical_source": "https://www.machinebrief.com/news/ray-cve-2025-62593-rondodox-botnet-developer-workstation", "published_at": "2026-08-23 13:04:51+00:00", "updated_at": "2026-08-23 13:14:11.987015+00:00", "lang": "en", "topics": ["ai-infrastructure", "ai-safety"], "entities": ["RondoDox", "Bitsight", "Ray", "Amazon", "Apple", "OpenAI", "CISA"], "alternates": {"html": "https://wpnews.pro/news/a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before", "markdown": "https://wpnews.pro/news/a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before.md", "text": "https://wpnews.pro/news/a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before.txt", "jsonld": "https://wpnews.pro/news/a-botnet-started-exploiting-a-critical-ray-flaw-two-days-before.jsonld"}}