Eleven days, 11.5 million tries: the leak that walked past MFA

By the zmam.ai team · · updated

Summary

  • CitrixBleed 2 (CVE-2025-5777) leaked session tokens from NetScaler memory, letting attackers replay a session and bypass MFA after the user had already passed it.
  • Exploitation began ~11 days before a public proof-of-concept; Imperva observed 11.5M+ exploitation attempts and 100+ organizations were compromised.
  • What an external scan would have shown: an exposed NetScaler gateway and its build number — and whether the appliance is end-of-life.

Multi-factor authentication is supposed to be the backstop. Even if a password leaks, the second factor holds the line. CitrixBleed 2 is the story of a bug that made the backstop irrelevant — not by defeating MFA, but by stealing the session after the user had already passed it.

A leak, not a break-in

On 17 June 2025, Citrix disclosed CVE-2025-5777 in NetScaler ADC and Gateway. The flaw is an out-of-bounds memory read: when the device is configured as a Gateway or AAA virtual server, a malformed request makes a backend parser hand back a chunk of uninitialized memory it should never have exposed. Sift through enough of those chunks and you find session tokens — the credentials a user receives after logging in and completing MFA. Replay a stolen token and you are that user, second factor and all. Researchers immediately recognized the shape: it is the same class of bug as the original 2023 CitrixBleed (CVE-2023-4966) that fueled a wave of ransomware, which is why this one was christened CitrixBleed 2.

The severity scores capture how the industry argues about these things: Citrix rated it 9.3 on CVSS v4.0, while NIST’s v3.1 score came in at 7.5. The attackers did not wait for the committee to settle it.

The eleven-day head start

This is the detail that should change how you think about exposed devices. GreyNoise observed exploitation in the wild beginning 23 June 2025 — roughly eleven days before a public proof-of-concept existed (watchTowr published on 4 July, Horizon3.ai on 7 July). CISA added the bug to its Known Exploited Vulnerabilities catalog on 10 July.

In other words, attackers were already draining session tokens from real appliances while the rest of the world was still waiting for the exploit to be “real.” Imperva later reported observing more than 11.5 million exploitation attempts, with around 40% aimed at financial services. The security researcher Kevin Beaumont, who named the bug, documented at least 100 compromised organizations across education, finance, government, legal, and telecom. As of mid-July, Shadowserver still counted thousands of unpatched instances; Censys put the total population of internet-exposed NetScaler systems near 70,000.

The pattern nobody wants to see

CitrixBleed 2 was not an outlier in 2025. It was a genre. The same year delivered:

Four different vendors, one shared DNA: an internet-facing management or VPN or file-transfer interface, fingerprinted at scale, hit before most defenders had finished reading the advisory.

What the outside view would have shown

None of these campaigns required clever reconnaissance. Attackers enumerated the exact surfaces a defender can see for free. From the outside, a non-intrusive scan can flag the preconditions without ever sending an exploit:

The uncomfortable lesson of 2025 is that “we’ll patch when the exploit is public” is a losing strategy when exploitation precedes the public exploit by eleven days. Knowing what you have exposed — and how old it is — is the part you control. That is exactly what an external attack-surface review, like the one zmam.ai is built toward, is for. See What is External Attack Surface Management? for the bigger picture.

Sources