Coordinated, Until It Isn't: Moksha's 89-vuln XAPI drop
Moksha's recent disclosure of 89 vulnerabilities in XAPI has sparked debate about the nature of coordinated disclosure. The decision involved multiple factors, including going public without an embargo and withholding patches from Citrix. This situation highlights the inherent risks researchers face compared to vendors in the disclosure process.
- ▪Moksha published 89 vulnerabilities in XAPI without an embargo and withheld patches from Citrix.
- ▪The reactions to this disclosure have been polarized, with some applauding the pushback and others condemning it as irresponsible.
- ▪The current system of coordinated disclosure places most of the legal and reputational risks on researchers, while vendors face minimal consequences.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | caseyjohnellis |
| Canonical URL | https://cje.io/2026/05/17/coordinated-until-it-isnt/ |
| Publication time | Sat, 30 May 2026 13:45:18 +0000 |
| Retrieval time | 2026-05-30T13:59:38.171Z |
| Last seen | 2026-05-30T13:59:38.171Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | xa242FhcJA14 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Policy Coordinated, Until It Isn't Everyone has a take on Moksha's 89-vuln XAPI drop. Almost everyone misses the same thing: it wasn't one decision, it was four: go public, go Day-0, withhold patches from Citrix, lean into the "shittrix" frame. Coordinated disclosure runs on goodwill, and the goodwill runs out sometimes. Casey Ellis 17 May 2026 — 9 min read Share Whenever I hear people say "Uncoordinated Disclosure" I immediately think of Mr Bean. Now you will too. You're welcome. A few weeks ago an independent researcher named Jakob Wolffhechel — operating as Moksha — published 89 vulnerabilities in XAPI, the management stack underneath Citrix XenServer and XCP-ng.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at caseyjohnellis.
Discussion
0 commentsMore from caseyjohnellis
