# Proof-of-concept exploit

GLOSSARY, read 10 Nov 2026

**Definition.** A proof-of-concept exploit is public code or a demonstration showing a vulnerability can be triggered. In CVSS v4.0, Exploit Maturity P means PoC code is publicly available with no reported attacks. A public PoC is evidence of feasibility, not of attacks.

CISA states that a public proof of concept is not required for KEV inclusion. A KEV entry rests on evidence of exploitation, which can come from sources that never publish code.

BOD 26-04 sets automatable to yes when a public proof of concept reliably achieves remote code execution. That makes the PoC a direct input to a due date.

## A sourced example

CISA's BOD 26-04 implementation guidance, last updated 2026-08-25, says a public proof of concept is not required for KEV inclusion.

## Related terms

- [Exploit maturity](/glossary/exploit-maturity/)
- [SSVC automatable](/glossary/ssvc-automatable/)
- [KEV dateAdded](/glossary/kev-date-added/)

## Sources

- Source for the example: Proof-of-concept exploit: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/glossary/proof-of-concept-exploit/
