# Vulnerability exception

GLOSSARY, read 10 Nov 2026

**Definition.** A vulnerability exception is the record in a platform that excludes a finding from overdue counts, either because it will not be fixed (accepted) or cannot be fixed yet. It carries a reason, a requester, an approver and an end date, and it should be visible in reports rather than hidden.

Exception volume is itself a program metric. A rising share of findings under exception can mean the service levels are unrealistic.

Request and approval flow are where platforms differ. Some run the request as an automated workflow with an approval step.

## A sourced example

On 2026-11-10 Brinqa's automation documentation described a workflow engine driven by queries, with exception requests, false positive requests and vulnerability ticket creation among its uses.

## Related terms

- [Risk acceptance](/glossary/risk-acceptance/)
- [False positive](/glossary/false-positive/)
- [Remediation SLA](/glossary/remediation-sla/)
- [Compensating control](/glossary/compensating-control/)

## Sources

- Source for the example: Vulnerability exception: https://docs.brinqa.com/docs/automation (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/vulnerability-exception/
