Citrix NetScaler session-token disclosure “Citrix Bleed”
An unauthenticated attacker reads valid session tokens straight out of NetScaler ADC/Gateway memory — then logs in as your users, MFA and all.
Today item, not a backlog item.
Known-exploited, weaponized with public proof-of-concept, and used by named ransomware crews against internet-facing edge appliances. If you run an exposed, unpatched NetScaler, assume-breach is the correct posture — not a patch window.
Is it exploitable?
— the evidence, ranked above the scoreWho’s exploiting it?
— attribution turns risk into urgencyCISA, FBI, and MS-ISAC jointly attribute active exploitation of Citrix Bleed to LockBit 3.0 affiliates, who use the stolen sessions to land, escalate, and deploy ransomware — naming it in a dedicated #StopRansomware advisory.4
Incident responders attribute Citrix Bleed exploitation beyond LockBit, including other ransomware and extortion crews, across finance, logistics, legal, and manufacturing victims. Treat this as a broadly-held capability, not a single-actor tool.6
Why it matters
— the attack path, told twice: adversary, then boardFront door — unauthenticated access narrative 1
Keys to the kingdom — identity takeover narrative 2
Data at risk — exfiltration narrative 4
Lights out — disruption & extortion narrative 5
What to do
— defensible action- Patch to the fixed build for your branch (14.1-8.50 / 13.1-49.15 / 13.0-92.19 or later); retire end-of-life 12.1. Per the vendor bulletin.5
- Patching is not enough — kill active sessions. Stolen tokens stay valid after the patch. Terminate all active and persistent ICA/PCoIP sessions (
kill icaconnection -all,kill pcoipConnection -all) as Mandiant and CISA direct.6 - Hunt for prior compromise on any appliance that was exposed and unpatched between disclosure and remediation — assume token theft already happened.4