Skip to content

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.

Current draft (work in progress): Draft 2

This specification is a draft, not a finished standard.

Property Value
Version draft-2
Status Current draft (work in progress), not yet released
Opened 2026-11-13
Last updated 2026-11-20

The last-updated date is the date of the publish of the site that built this page: each publish stamps it. The opened date is the day the entry for this draft was added to the drafts register. The drafts register, which the Revision Log is generated from, records each draft's dates. Until a release of the Vultron repository carries the draft, its text can still change. To cite this text, name the specification, the version and the date it was last updated, for example: Vultron Protocol Specification, draft-2, 2026-11-20. Until a release carries the draft, also name the publish-YYYY-MM-DD.N tag in the page footer, which identifies the text you read (Vultron Release Versioning). Once a release carries the draft, name the release tag that the Revision Log gives for it instead. The newest released draft is draft-1, which release v2026.11.0 carries; the Revision Log links its frozen copy.

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.

The Requirements Catalog is published one theme per page:

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.

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.

Path overview