#citrixbleed2
Live, measured metrics for the hashtag #citrixbleed2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #citrixbleed2
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 15:31 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 15:31 UTCNo related tags with measured usage found for #citrixbleed2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 15:31 UTCEverything below is measured over the latest 40 public posts (spanning ~4567 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (36) · German (4)
Avg boosts / post: 3.3
Top of the latest posts
With the #CitrixBleed2 patch data I publish it's possible to view the history on Github for each new scan and see when hosts change from vuln to patched. It's proving incredibly effective at getting orgs to patch. I tried private notificati
Emerging situation to be aware of - some of the #CitrixBleed2 session hijacking victims are also victims of webshell implants via a different vuln, CVE-2025-6543. Script to check for Netscaler implants: https://github.com/NCSC-NL/citrix-202
The Dutch Public Prosecution Service (OM), which took their systems offline due to #CitrixBleed2 on Friday, are saying they will be offline for weeks. https://nos.nl/artikel/2575857 HT @moartn
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/citrixbleed2