Vultron Protocol Specification
The whole specification on one page
The specification is also published as a single page that holds every section and annex in order, for printing or for searching the whole text at once.
Status: Draft 1, released in v2026.11.0
This specification is a draft, not a finished standard.
| Property | Value |
|---|---|
| Version | draft-1 |
| Status | Released in v2026.11.0 |
| Date | 2026-11-06 |
The date is the day the entry for this draft was added to the drafts register, which the Revision Log is generated from.
Release v2026.11.0 of the Vultron repository carries this draft, so its text no longer changes: a change goes into the next draft.
To cite this text, name the specification, the version, the date and the release tag, for example: Vultron Protocol Specification, draft-1, 2026-11-06, v2026.11.0.
Abstract
The Vultron Protocol coordinates vulnerability disclosure among multiple organizations. Participants exchange asynchronous messages and track the case across four dimensions of shared state, realized as five state machines. Any number of organizations may take part in a single case.
Coordination is scoped to the case rather than to a system: the case-management role is held per case, and different cases may be managed by different actors. No single service holds every case. Within a case, one participant holds write authority over the case's shared state, so that concurrent claims resolve to one answer.
Parts
The specification is published one part per page. The parts are listed in reading order, and each page holds the sections listed beside it, from the introduction to the Internet Assigned Numbers Authority (IANA) and security considerations.
- Introduction and Overview: §1 Introduction, §2 Terminology, and §3 Protocol Overview.
- Messages and Encoding: §4 Messages and §5 Encoding and Transport.
- Case Tracking Models: §6 Report Management (RM) State Machine, §7 Embargo Management (EM) State Machine, §8 Case State (CS) Dimensions, and §9 Participant Embargo Consent (PEC) State Machine.
- Coordination, Interactions, and Lifecycle: §10 Case Coordination, §11 Model Interactions and Cascade Rules, and §12 Participant Lifecycle Within a Case.
- Conformance: §13 Conformance.
- Requirements Catalog: §14 Requirements Catalog, which lists every
protocolandfoundationrequirement once. - Considerations and References: §15 IANA and Namespace Considerations, §16 Security Considerations, and §17 References.
The Requirements Catalog is published one theme per page:
- §14.1 Vultron Protocol
- §14.2 Messages and Vocabulary
- §14.3 Report, Embargo and Case State Behavior
- §14.4 Case Management
- §14.5 Case Ledger and Replication
- §14.6 Message Processing
- §14.7 Transport and Security
- §14.8 Inherited Requirements
Annexes
The annexes illustrate and explain the protocol, and nothing in them is normative.
Annexes A and B trace Coordinated Vulnerability Disclosure (CVD) cases from first contact to closure.
- Annex A Worked Example: Single-Vendor CVD
- Annex B Worked Example: Multi-Party CVD
- Annex C Notation Reference
- Annex D Possible Case Histories
- Annex E Relationship to ActivityPub
- Annex F Behavior Trees as an Implementation Pattern
- Annex G Capability Shapes
Open Questions, Known Gaps, Revision Log, and the Single-Page Edition
Open Questions collects the questions this draft of the specification leaves unresolved.
Known Gaps lists the requirements that the tests do not show the reference implementation's main branch fully meets.
The Revision Log records each draft of the specification, its version identifier and date, and what changed in it.
The single-page edition holds every section and annex in order, for printing or for searching the whole text at once.
Reading path: You maintain a vulnerability tracker and want it to talk to your partners
This page is part of Build against the contract.
Previous