Glossary

Coordinated vulnerability disclosure

CVD

Definition

A process for reporting a security weakness privately and coordinating a fix and public information with the affected supplier.

A clear reporting route lets someone who finds a weakness contact the responsible team safely. The organization needs an owner who can investigate, coordinate a fix and communicate with affected people.

A customer may include “Coordinated vulnerability disclosure” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

Coordinated vulnerability disclosure gives someone who finds a security weakness a way to report it to the responsible supplier. The parties then work on understanding the problem, reducing exposure and communicating useful information to affected customers.

For example, a researcher may discover that a booking service reveals another customer's reservation. A published reporting address and an agreed process can help the supplier confirm the issue and fix access checks before wider disclosure increases exposure.

A disclosure policy should explain which systems are covered, what testing is permitted and how reports will be acknowledged. It is different from a bug bounty, which offers rewards under specified rules. Neither is permission to test systems outside that scope.

Publish a clear route for security researchers to report vulnerabilities, acknowledge reports and coordinate fixes before broad disclosure. Define how mitigation reaches affected customers; a reporting policy does not prove software is free of flaws. A confidential report is only useful if someone owns the response.

Sources: NCSC: vulnerability disclosure toolkit.