# SSVC automatable

GLOSSARY, read 10 Nov 2026

**Definition.** SSVC automatable is a decision point asking whether an attacker can reliably automate the steps from reconnaissance to a working exploit across targets. Values are yes and no. BOD 26-04 sets it to yes when a public proof of concept reliably achieves remote code execution.

It captures scale, which neither CVSS base nor EPSS records directly. A flaw that scans and exploits with a script reaches many targets at once.

BOD 26-04 uses it as one of four inputs to the due date. Where it is missing for a CVE not in KEV, CISA treats it as no.

## A sourced example

The NVD record for CVE-2026-41709 (Broadcom VMware ESX, KEV dateAdded 2026-10-28) carries automatable no and a 14-day due date, while CVE-2026-33824 carries automatable yes and a 3-day due date.

## Related terms

- [SSVC technical impact](/glossary/ssvc-technical-impact/)
- [SSVC exploitation](/glossary/ssvc-exploitation/)
- [BOD 22-01](/glossary/bod-22-01/)

## Sources

- Source for the example: SSVC automatable: https://nvd.nist.gov/vuln/detail/CVE-2026-41709 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/glossary/ssvc-automatable/
