Cybersecurity

Six Days, Three Critical Flaws, Zero Grace Period

Ray, GitLab and Apple all disclosed critical, unauthenticated remote-exploit flaws in six days in August 2026, each mass-exploited within days of a patch.

CybersecurityBy Servola Tech Desk2026-08-183 min read

AI-assisted, edited by humans. | Editor-in-Chief: Leon Soliman | Editorial standards

Six Days, Three Critical Flaws, Zero Grace Period

Key takeaways

Ray's DNS-rebinding flaw (CVSS 9.4) was weaponized by the RondoDox botnet two days before public disclosure, and GitLab's unauthenticated GraphQL bug (CVSS 9.4) and Apple's Screen Sharing bypass (CVSS 9.8) both followed the same pattern in the same week.
CISA added the Ray flaw to its Known Exploited Vulnerabilities catalog on 17 August 2026, giving US federal agencies until 20 August 2026 to patch.
Apple's macOS Screen Sharing bypass went from a 6 August patch to a CISA severity score of 9.8 by 14 August, after NCSC-NL confirmed attackers were gaining root access and installing Monero miners on internet-exposed Macs.
GitLab's flaw is the platform's third critical GraphQL vulnerability disclosed in 2026, and self-hosted GitLab CE/EE instances, not GitLab.com or GitLab Dedicated, are the ones left exposed.
A separate campaign, ShadowRay 2.0, specifically hunts unpatched Ray clusters running on NVIDIA GPUs to build cryptocurrency-mining botnets, showing attackers are now targeting AI training infrastructure for its compute power.

Three Unrelated Vendors, One Identical Timeline

Ray is an open-source, Python-native framework used to run AI and ML training and inference workloads, with more than 43,500 GitHub stars and wide use inside enterprise AI infrastructure. A flaw tracked as CVE-2025-62593, with a CVSS score of 9.4, let an attacker combine DNS rebinding with an ordinary browser visit to make a developer's own machine submit code-execution requests to a local Ray cluster, because the authentication check on Ray's API endpoints only verified that the User-Agent header started with the word Mozilla, a value any browser sends by default.

GitLab, the source-control and CI/CD platform used across the industry, disclosed CVE-2026-19478 on 17 August 2026: a GraphQL directive with a CVSS score of 9.4 that let an unauthenticated attacker modify or delete public projects and user data over the network with no user interaction required. Apple patched CVE-2026-65400 on 6 August 2026, a state-management flaw in the credential validation of macOS Screen Sharing, the built-in remote-desktop service that listens on network port 5900. Three unrelated organizations, three unrelated products, one six-day window.

From Patch to Mass Exploitation in Days, Not Months

The RondoDox DDoS botnet incorporated a working exploit for the Ray flaw on 24 November 2025, two full days before the flaw was even publicly disclosed on 26 November 2025, because a proof-of-concept was already circulating. A second campaign, ShadowRay 2.0, specifically scans for unpatched Ray clusters running on NVIDIA GPUs and turns them into self-replicating cryptocurrency-mining botnets, which shows attackers are now deliberately targeting AI training infrastructure for its raw compute power rather than treating it as a generic server.

Apple's Screen Sharing flaw followed the same acceleration. The patch shipped on 6 August 2026, the Netherlands' National Cyber Security Centre confirmed active exploitation against internet-exposed Macs, and in every confirmed case the attacker gained root access and installed a Monero cryptocurrency miner. CISA raised the flaw's severity score from 7.1 to 9.8 on 14 August 2026, eight days after the patch, once it confirmed the exploit had become automatable at scale. CISA added the Ray flaw to its Known Exploited Vulnerabilities catalog on 17 August 2026, with US federal civilian agencies given until 20 August 2026 to patch.

What This Means for Your Patch Cadence

None of this is exotic. Ray sits on AI training clusters, GitLab sits on the software supply chain, and Screen Sharing sits on every Mac an IT team manages remotely, three ordinary pieces of infrastructure that most organizations already run. The gap that used to exist between a vendor releasing a patch and criminals exploiting it at scale has been shrinking for a while, and the Ray timeline shows it can now be negative: the exploit was weaponized before the public even knew the flaw existed.

A monthly or quarterly patch cycle is no longer a defensible security posture for anything with a network-facing admin or developer surface, and self-hosted GitLab, AI training clusters and remotely-managed Mac fleets all fall squarely into that category. The practical response is to track days-from-patch-release-to-full-deployment as a tracked, board-level metric for each of these three categories, with particular attention to self-hosted AI and ML infrastructure, since it is a newer category and most security teams have not yet built a fast patch process for it.

Frequently asked questions

Are these three flaws connected or part of the same attack?

No. Ray, GitLab and Apple are unrelated products from unrelated organizations. What connects them is timing: all three had critical, unauthenticated, remotely exploitable flaws disclosed or escalated to active mass exploitation within the same six-day window of 13-18 August 2026.

Do we need to worry about this if we use GitLab.com instead of self-hosting?

GitLab.com and GitLab Dedicated were already patched by the time the flaw (CVE-2026-19478) was disclosed. Self-hosted GitLab CE/EE instances running versions 18.2 through 19.2.3 are the ones exposed and need the update to 18.11.11, 19.0.8, 19.1.6 or 19.2.4.

How urgent is the Apple Screen Sharing flaw for us?

If any Mac in your fleet has port 5900 reachable from the open internet, treat it as urgent. NCSC-NL confirmed active exploitation gives attackers root access and installs a Monero miner, and CISA raised its severity score to 9.8 on 14 August 2026 after confirming the exploit had become automatable at scale. Apple's fix has been available since 6 August 2026.

The pattern across Ray, GitLab and Apple is the same lesson stated three times in one week: a patch sitting unapplied is not a paperwork item, it is an open door with a countdown attached. Owners who still treat patching as a monthly or quarterly cycle are measuring their risk with the wrong clock, and the fix is organizational, not technical: track days-to-patch as a board-level number for every network-facing admin or developer surface, starting with self-hosted AI infrastructure, source control and remote-access services.

RayGitLabAppleCISAAI InfrastructurePatch Management

Gunra Ransomware Runs on Fortinet Bugs Patched in 2025

CISA, the FBI, NSA and South Korea jointly named Gunra ransomware on August 10. It breaks in through two Fortinet flaws patched over a year ago. The real finding is patch lag, not the malware.

3 min read

Cybersecurity

TeamCity Flaw Lets Attackers Own Your Build Pipeline

CISA confirms active exploitation of CVE-2026-63077, an unauthenticated RCE in JetBrains TeamCity On-Premises. CVSS 9.8, KEV-listed 5 August, FCEB deadline 8 August.

5 min read

Decisions

The Third Pivot Was the Warning Magic Leap Missed

Magic Leap filed a WARN notice for 193 layoffs effective 1 October 2026, its fourth strategic pivot after $4 billion raised. The lesson is the pattern, not the pivot.

4 min read

← All articles