The long weekend in review: Glasswing found 10,000 vulnerabilities

THE BIG ONE: GLASSWING'S 10,000

Anthropic disclosed on Friday that Project Glasswing, its defensive initiative to secure critical global software infrastructure, has uncovered more than 10,000 high or critical severity vulnerabilities across some of the world's most systemically important software since the program went live last month. Of those, 6,202 were classified as high or critical severity impacting widely used software. Glasswing grants a small group of roughly 50 partners early access to Claude Mythos Preview, a frontier model that autonomously identifies vulnerabilities in widely deployed software before attackers find them.

The takeaway. This is the defender side of the story the Atarus blog has been documenting on the attacker side for six weeks. The GTIG AI Threat Tracker showed AI developing the first confirmed zero-day exploit. The bipartisan lawmaker letter cited Mythos and Glasswing by name. The Verizon DBIR measured the speed asymmetry. Glasswing is the attempt to close that asymmetry from the defender side. The 10,000 number is the proof the capability is real in both directions. The open question for every organization is what happens when those 10,000 vulnerabilities enter coordinated disclosure and the patching clock starts.

SUPPLY CHAIN: LARAVEL-LANG BACKDOORED

Researchers at Socket flagged a fresh supply chain attack against the Laravel-Lang PHP ecosystem. Credential-stealing remote code execution backdoors were injected into 233 package versions, with more than 700 versions republished in rapid succession on May 22 and 23, many appearing only seconds apart. The pattern points to a compromise of the Laravel-Lang organization's release process rather than a single malicious version, likely through stolen organization-level credentials or release automation access.

The takeaway. This is the same playbook the Atarus blog documented in the GitHub TeamPCP compromise and the Checkmarx campaign. Compromise the release infrastructure, mass-publish poisoned versions, harvest credentials downstream. The developer tooling supply chain remains the most active attack surface against the highest-value targets. If you run PHP and pull Laravel-Lang packages, audit your dependency versions from the May 22-23 window and rotate any credentials accessible to affected build environments.

ACTIVE EXPLOITATION: A FULL SLATE

The weekend produced a heavy run of active exploitation and emergency patching. NGINX disclosed CVE-2026-9256, a new flaw in one of the world's most widely deployed web servers, forcing administrators into another emergency patch cycle. A multi-stage intrusion was documented using an internet-facing F5 BIG-IP edge appliance as the entry point for a widespread, identity-focused attack. The LiteSpeed cPanel plugin CVE-2026-48172 was abused for root access. And the Drupal core SQL injection CVE-2026-9082, which Atarus flagged was at risk of rapid exploitation when it was disclosed, is now being actively exploited against thousands of websites.

The takeaway. The Drupal timeline is the Verizon DBIR finding in miniature. Disclosed May 20, actively exploited against thousands of sites by the weekend. The window from disclosure to exploitation is measured in days, sometimes hours. Edge appliances, web servers, and CMS platforms remain the perennial initial-access targets. If any of NGINX, F5 BIG-IP, LiteSpeed, or Drupal are in your stack, this is the short week to verify your patch status against the weekend disclosures.

THE WINS: TWO TAKEDOWNS

Two pieces of good news worth noting. Financial crime investigators in the Netherlands arrested two men and seized 800 servers linked to a bulletproof hosting company that enabled cyberattacks, interference operations, and disinformation campaigns. Separately, authorities dismantled a global VPN service linked to 25 ransomware groups. Both actions disrupt the infrastructure layer that criminal operations depend on.

The takeaway. Infrastructure takedowns matter because they raise the cost of operating for the criminal ecosystem. They do not end the threat, but they impose friction. The Atarus narrative has consistently been that the invisible cyber war is fought on both sides. The weekend was a reminder that the defender side, both the AI-augmented vulnerability discovery of Glasswing and the boots-on-the-ground law enforcement work in the Netherlands, is also making moves.

WHAT TO WATCH THIS WEEK

Three things on the radar for the short week. First, the June 4 CISA KEV remediation deadline for the Trend Micro Apex One zero-day and the Langflow flaw Atarus covered Friday. Federal agencies are on the clock and private-sector defenders should be too. Second, any escalation of the Laravel-Lang compromise as researchers map the full scope of the affected versions. Third, the downstream effects of the Glasswing disclosure as the security community digests what 10,000 AI-discovered vulnerabilities means for the coordinated disclosure pipeline and the patching burden ahead.

The Atarus blog returns to its daily cadence tomorrow. This weekend recap is a new format we are trialing. If it is useful, we will keep it. The goal is simple. When the news does not stop for the holiday, neither should the catch-up.

ATARUS ASSESSMENT

The long weekend reinforced the throughline the body of work has been tracking. The Glasswing disclosure is the most important single item. Ten thousand vulnerabilities found by an AI system in a month is the defender-side mirror of the attacker capability the GTIG report documented and the lawmaker letter named. It validates the central argument that the capability is real and that the question is no longer whether AI changes vulnerability discovery but how fast defenders can operationalize it relative to attackers. The Laravel-Lang compromise confirms the supply chain remains the dominant attack surface. The active exploitation slate confirms the speed asymmetry the Verizon DBIR measured. The enforcement actions confirm the defender side is not passive. For practitioners, the short week is a patching week. The June 4 KEV deadline, the weekend disclosures, and the ongoing Drupal exploitation all point to the same work. Verify patch status, prioritize the KEV catalog, and treat the disclosure-to-exploitation window as days rather than weeks. The protection of the systems communities depend on is the work, and it does not pause for a holiday.