NCC Group: an LLM pipeline found two etcd authorization bypasses
A code graph, an LLM and live etcd instances produced two confirmed authorization bypasses, each with a CVE and a patch.
· NCC Group · Research by Luis Toro Puig
NCC Group published on October 6, 2026 how an LLM-assisted pipeline found two authorization bypasses in etcd, both since fixed: a revocation list skipped on the gRPC listener, and a Watch API range that ignored RBAC.
01What happened
NCC Group researcher Luis Toro Puig described the pipeline and its results in a research post on October 6, 2026. The two flaws it produced, CVE-2026-59818 and CVE-2026-73499, went through etcd's own security advisories on July 1 and July 23, 2026 and are fixed. For the Watch API flaw, etcd credits Luis Toro alongside Anthropic and Adam Korczynski as reporters.
02How it works
Five stages make up the pipeline: graphify indexes the etcd repository into a code graph at a fixed commit, an LLM explores that graph to generate security hypotheses, live etcd instances built from the same revision validate them, each hypothesis is confirmed or rejected, and a report is generated. Validation against a running cluster is what separates a confirmed finding from a model's guess. NCC Group's post does not name the model it used.
03Who is affected
etcd clusters on the affected builds were exposed, and every affected branch now has a patched release, listed above. Neither flaw involves an AI product: etcd is the key-value store behind Kubernetes, and the AI part of this story is the discovery method. Teams judging AI-assisted vulnerability research are the audience for the pipeline itself.
04What to do
Run etcd 3.7.1, 3.6.14 or 3.5.33 or later, which carry both fixes. Clusters that split client endpoints with --listen-client-http-urls and rely on --client-crl-file should confirm the upgrade, because the revocation list was the control that failed there.
Sources 3 links, all fetched
- 1nccgroup.comNCC Group Research
- 2github.cometcd CRL Advisory
- 3github.cometcd Watch Advisory