The Chaos of Coordinated Disclosure: Researchers Tell All (Panel)
Coordinated vulnerability disclosure was built for a world where a handful of researchers reported bugs one at a time. That world is gone. AI-assisted discovery is multiplying the volume of findings, research teams are colliding on the same bugs independently, and vendors are struggling to keep pace with response timelines built for a slower era. This panel brings together veteran voices in vulnerability research and disclosure policy to dig into what coordination actually means in practice, not just in theory, and how researchers, vendors, and platforms should adapt. Expect candid, practitioner-level discussion on disclosure deadlines, vendor silence, undisclosed patches, and when publishing a public proof-of-concept is the right call.
Discussion Topics: Setting the stage, the history of vulnerability disclosure. How we got from ad hoc reporting to formal CVD frameworks, and what problems those frameworks were actually built to solve. What does "coordination" actually mean? Unpacking the gap between the ideal of CVD and how it plays out between researchers, vendors, and coordinating bodies in practice. Reporting a vulnerability today. What a good report looks like, and how researchers and suppliers should approach coordinated disclosure from the first email onward. Research collisions. What happens when multiple researchers (or an AI tool and a human) independently find the same bug: attribution, timelines, and who "owns" disclosure. AI vulnerability discovery. How AI-assisted discovery is changing volume, speed, and the coordination burden on both researchers and vendors. When things break down. What should you do if a vendor goes silent? What should you do when a vendor patches but doesn't disclose? Publishing a public PoC. When is the right time to publish a Proof-of-Concept or Exploit?