Safeguard
Security Guides•

Exploit intelligence terms defined: PoC, in the wild, KEV, EPSS

Plain definitions of proof of concept, exploitable, wormability, in the wild, attempted exploitation, KEV, EPSS, percentile and more, from CISA and FIRST.

Safeguard Security Team
4 min read

Exploit intelligence has its own vocabulary, and terms like exploitable, exploited and exploit available are often confused. This glossary defines the main ones in plain words, using definitions from CISA and FIRST where they exist, so your team and your reports use each word the same way.

The terms

TermPlain definition
CVEA unique, common identifier for a publicly known security flaw, assigned by a CVE Numbering Authority
ExploitableHow easily an attacker can take advantage of a flaw, considering a public proof of concept, network access, privileges, wormability and skill needed (CISA's description)
WormabilityAn attack that can spread from one machine to another without user interaction
Proof of concept (PoC)Code for a flaw that, when run, would allow exploitation; shared between researchers and vendors, and sometimes made public
Exploit framework moduleA packaged exploit for an open source framework, a more operational form than a raw PoC
Scanner templateA definition of a check for a scanning engine, which can test many targets quickly
Exploited, or active exploitationReliable evidence that malicious code was executed against a system without the owner's permission; includes attempts and successes
Attempted exploitationAn attacker runs code against a target but it does not succeed, for example because the system is not vulnerable or is a honeypot
Successful exploitationThe attacker succeeds and takes unauthorized actions on the system or network
In the wildHappening in real time against real targets, not in a lab
HoneypotA decoy system set to detect or counteract attempts at unauthorized use
KEVCISA's Known Exploited Vulnerabilities catalog, a curated list with reliable exploitation evidence and a remediation action
EPSSA model from FIRST that estimates the probability of observed exploitation activity in the next 30 days
EPSS percentileThe proportion of scored vulnerabilities with the same score or lower
Base rateThe share of vulnerabilities that see exploitation in a period; FIRST gives roughly 2 to 3 percent for 30 days

Three pairs people mix up

Exploitable versus exploited. Exploitable is about ease. Exploited is about events. CISA says exploitability is not a criterion for KEV, which asks whether exploitation actually happened.

PoC versus attack. CISA says a public PoC does not automatically mean a flaw has been or will be exploited. It can raise the likelihood.

Scanning versus exploitation. CISA lists scanning as not active exploitation. Running exploit code at a target is.

Two more that matter

Probability versus percentile. The probability is the absolute estimate. The percentile is a ranking. Because most scores are tiny, a 10 percent probability sits near the 95th percentile, per FIRST's FAQ.

Forecast versus record. KEV is a record of past confirmed exploitation. EPSS is a forecast. A low forecast on a listed item is not a contradiction.

Using the glossary

  1. Paste it into your vulnerability policy as an appendix.
  2. Require reports to use these words, so a ticket that says exploited means the KEV or vendor meaning, not a PoC.
  3. Review it each year. CISA and FIRST may update their pages.

A shared vocabulary reduces arguments. When someone says "it is exploitable", ask: do you mean easy to exploit, or known to be exploited? The answer changes the response.

Safeguard's reachability analysis, SBOM and dependency scanning and policy gates help turn these definitions into checks on your own code. You can try a free scan at gold.safeguard.sh/scan.

Try it yourself

Click through it at your own pace, or open it full screen.

As you click, notice which of the terms above each piece of evidence would map to.

Quick check

Is exploitable the same as exploited?

No. Exploitable is about how easy an attack is. Exploited means there is reliable evidence it was used. CISA keeps them apart in its KEV criteria.

Does a honeypot hit count as exploitation?

For KEV, CISA treats it as attempted exploitation, which counts as active exploitation. It is not a successful compromise of a real target.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.