Sentinel Brief

CitrixBleed 2: Ransomware Deployed in Under 60 Minutes

data center server rack network equipment - black and gray dell computer tower

Photo by Samuel Ramos on Unsplash

Less than 60 minutes. That is the documented gap between a threat actor gaining initial access through CVE-2025-5777 — a critical flaw in Citrix NetScaler devices now tracked as CitrixBleed 2 — and ransomware detonating across an organization's entire domain. As of July 10, 2026, security research firm Huntress has confirmed this timeline across at least six unrelated organizations, and reporting by Google News documents that a criminal ecosystem has coalesced around this attack chain with industrial efficiency. This is not an isolated incident. It is a productized criminal service.

The Threat — CVE-2025-5777 and the 7-Stage Runbook

CVE-2025-5777 is a pre-authentication memory disclosure vulnerability — a flaw that allows attackers to read sensitive server memory without logging in first — affecting Citrix NetScaler ADC and Gateway devices configured as Gateway or AAA virtual servers. Its CVSS score is 9.3 out of 10. The exploit enables an unauthenticated attacker to extract live session tokens from device memory and replay them to hijack authenticated sessions, including sessions that have already cleared multi-factor authentication. MFA provides no protection once a token is stolen at the network layer — the session is already authenticated when the attacker intercepts it.

Huntress investigated at least six intrusions at unrelated organizations between January and June 2026, mapping a repeatable seven-stage attack chain. In the most alarming case their Tactical Response team handled, ransomware was deployed in less than 60 minutes from initial access. The team's assessment was unambiguous: “The speed the adversary operated with was their singular advantage — ransomware was deployed almost immediately following the execution of the local privilege escalation script — leaving little time for defenders to respond.”

The consistency of this playbook across unrelated victims points to an Initial Access Broker (IAB) — a criminal specialist who compromises environments and sells that access to ransomware affiliates operating as a separate business unit. Huntress assesses with high confidence that an IAB is weaponizing CVE-2025-5777 specifically to gain footholds in Citrix environments before handing off to the Anubis ransomware group. Their researchers described the pattern plainly: “When you see a kill chain reproduced this faithfully across unrelated environments, you are not looking at a coincidence. You are looking at an operator following a runbook. Almost certainly an initial access broker or ransomware affiliate who has productized this exact path from internet-facing Citrix box to domain-wide encryption.”

The Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-5777 to its Known Exploited Vulnerabilities (KEV) Catalog on July 10, 2025 — a formal signal of confirmed, active in-the-wild exploitation. GreyNoise documented exploitation activity beginning June 23, 2025, nearly two weeks before any public proof-of-concept code was released, which means attackers had working private exploits while defenders were still waiting for technical details to even begin building detection rules. As of July 10, 2026, Imperva has tracked 11.5 million CitrixBleed exploitation attempts globally since public disclosure.

Blast Radius — Who Needs to Pay Attention Right Now

If your organization runs internet-facing Citrix NetScaler ADC or Gateway appliances, you are in the blast radius. Healthcare, business services, and financial sectors have been the primary targets. Based on threat intelligence current as of July 10, 2026, more than 50% of CitrixBleed 2 victims are located in the U.S., followed by the U.K., Australia, France, and Canada. The Anubis ransomware group has claimed 91 victims through CitrixBleed 2 exploitation, with 11 of those reported in June 2026 alone — a single-month concentration that signals the IAB operation is accelerating, not winding down.

Anubis Ransomware: CitrixBleed 2 Victim Count (as of July 2026)025507510091Total VictimsClaimed by Anubis11June 2026 AloneSingle-Month Surge

Chart: Anubis ransomware group victim counts attributed to CitrixBleed 2 exploitation as of July 2026, sourced from Huntress research and threat intelligence reporting. Scale represents victim count, maximum axis value 100.

The consequences carry names and patient counts. Singing River Health System in Mississippi confirmed a December 2025 breach affecting 53,888 patients, with Social Security numbers, treatment records, and bank account information among the exposed data — a documented floor for what a single CitrixBleed intrusion costs a healthcare organization in patient harm and regulatory exposure.

The attack surface has expanded since the initial disclosure wave. NetScaler versions 12.1 and 13.0 are End-of-Life and will not receive patches for CitrixBleed vulnerabilities. Organizations running those builds are permanently exposed until they migrate to supported versions — and no future patch release will change that. On June 30, 2026, a third CitrixBleed-class flaw, CVE-2026-8451, targeting SAML-configured NetScaler appliances, was publicly disclosed. Threat actors exploited it within 24 hours of the patch release, compressing the available response window to almost nothing. DragonForce ransomware has also been observed routing command-and-control traffic through Microsoft Teams connections inside CitrixBleed 2 attack chains, specifically to hide malicious communications inside legitimate enterprise traffic and defeat destination-based detection rules tuned to flag unusual outbound destinations.

In my analysis, what separates CitrixBleed 2 from a typical critical CVE is the IAB layer sitting between vulnerability and encryption. When a criminal service has packaged the full path from “internet-facing Citrix box” to “domain-wide encryption” into a reproducible runbook, organizational response time is no longer a strategic variable. It is under an hour — and shrinking.

The Defense Stack That Changes the Math

The seven-stage playbook has identifiable chokepoints. Blocking any single stage is not the goal — making each stage expensive enough that the IAB operation routes toward softer targets is.

Technology control: Patch NetScaler devices to the latest supported firmware build immediately. Organizations on versions 12.1 or 13.0 should treat those appliances as already compromised and initiate migration without delay — no remediation patch is coming for End-of-Life builds. Network segmentation is a critical compensating control when patching must be deferred: Citrix Gateway systems should not have unfiltered east-west access to domain controllers or backup infrastructure, both of which are key escalation waypoints in every documented CitrixBleed kill chain. Denying lateral movement at that layer forces the attacker to expose themselves to additional detection events.

Process control: Both GreyNoise and Huntress documented active CitrixBleed 2 exploitation before public proof-of-concept code appeared. That pattern — commercial threat intelligence ahead of public disclosure — is precisely why structured threat intelligence (tracking IOCs, or indicators of compromise, alongside TTPs, tactics techniques and procedures) is non-negotiable for organizations running Citrix infrastructure. Incident response playbooks should include a specific “NetScaler anomaly” trigger that routes immediately to live analyst review. Automated SIEM alerts that feed a standard ticket queue with a four-hour SLA are operationally useless against a dwell time measured in minutes. This is a gap that costs nothing to fix with a single escalation-path update — ship that control today.

People control: Security awareness training for IT staff and leadership should explicitly address MFA bypass through session token theft. The assumption that MFA is a sufficient backstop against account takeover is widespread and, in the context of CitrixBleed, incorrect. Tabletop exercises that simulate a “Citrix anomaly to domain-wide ransomware” scenario will surface gaps in detection and escalation chains before a threat actor does — and this particular scenario has a documented real-world template to model from.

AI-based detection adds a meaningful layer here. Transformer-based models and random forest classifiers trained on lateral movement behavioral baselines can flag the CitrixBleed kill chain's signatures — credential dumping, rapid privilege escalation, atypical administrative tool execution in sequence — faster than static rule-based detection. Security vendors are incorporating explainable AI techniques, specifically LIME and SHAP methods that identify which behaviors triggered an alert, to reduce false positives in rapid-escalation scenarios without increasing analyst fatigue. The adversary may also be applying AI to optimize reconnaissance timing and target selection, which would further compress the already narrow response window in future campaigns — making real-time behavioral detection a necessity, not a differentiator.

Harden This Today

One control. Ship it before end of business.

Invalidate all active sessions on your NetScaler appliances system-wide and force re-authentication — then immediately apply the latest patched firmware build. CVE-2025-5777 allows stolen session tokens to persist and be replayed against your environment even after patching, because the token was authenticated before the patch was applied. Patching without first clearing active sessions leaves previously stolen tokens viable for continued use. Clearing sessions first, then patching, closes the session-hijacking vector the IAB runbook depends on. If the firmware update cannot be completed today, segment the appliance from domain controller access as a compensating control until patching is finished. This sequence — session invalidation, then patching, then verification — is the one action that materially reduces your CitrixBleed 2 exposure before any other incident response work begins.

Frequently Asked Questions

What is the CitrixBleed 2 vulnerability and how does CVE-2025-5777 enable ransomware deployment so quickly?

CitrixBleed 2 (CVE-2025-5777) is a pre-authentication memory disclosure flaw in Citrix NetScaler ADC and Gateway devices, carrying a CVSS score of 9.3 out of 10. An unauthenticated attacker sends crafted requests that cause the device to expose portions of server memory containing live session tokens. Those tokens represent sessions that have already passed multi-factor authentication, so replaying them grants full authenticated access without credentials or MFA codes. From that initial foothold, a documented seven-stage attack playbook escalates privileges and deploys ransomware — in confirmed cases investigated by Huntress, in under 60 minutes.

How does CitrixBleed 2 compare in severity to the original CitrixBleed vulnerability from 2023?

Both are rated critical, but CitrixBleed 2 has a more developed criminal ecosystem. The original CitrixBleed (CVE-2023-4966) was exploited as a zero-day from August 2023, with mass attacks erupting after October 2023 patches, ultimately breaching Boeing, the Industrial and Commercial Bank of China (ICBC), and DP World via LockBit ransomware. CitrixBleed 2 now has an active IAB running a reproduced seven-stage runbook and an associated ransomware group — Anubis — with 91 claimed victims as of July 2026. The documented sub-60-minute dwell time makes it operationally more dangerous than its 2023 predecessor.

Which NetScaler versions are affected, and do I need to patch CitrixBleed 2 immediately?

CVE-2025-5777 affects NetScaler ADC and Gateway appliances configured as Gateway or AAA virtual servers. NetScaler versions 12.1 and 13.0 are End-of-Life and will not receive security patches — organizations on those builds must migrate to supported versions and should treat current appliances as compromised. For supported versions, the answer is yes: patch immediately. CISA's Known Exploited Vulnerabilities designation, GreyNoise's documentation of exploitation that preceded public proof-of-concept code, and Imperva's count of 11.5 million global exploitation attempts all confirm this is an actively weaponized vulnerability with no grace period for scheduled patching windows.

Bottom line: As of July 10, 2026, CitrixBleed 2 is a fully industrialized criminal pipeline — a seven-stage runbook executed by an IAB with the operational consistency of a logistics company, compressing the gap from initial access to domain-wide encryption to under 60 minutes. Anubis claims 91 victims. CISA has formally flagged it. Imperva has counted 11.5 million exploitation attempts globally. A third CitrixBleed-class vulnerability was exploited within 24 hours of its patch release. If you run internet-facing NetScaler appliances, the two actions that matter most are session invalidation and patching — in that order, before business closes today.

Disclaimer: This article is for informational and editorial purposes only and does not constitute professional security consulting advice. Always consult with a qualified cybersecurity professional for your specific environment and needs. Research based on publicly available sources current as of July 10, 2026.