> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/introduction-to-xygeni/prioritization-funnels/prioritization-funnels-1/exploitability.md).
# Exploitability
## Exploitability
Given we found an issue with a CVE, we should first know if it is reachable (as seen above). But even when reachable, **what is the likelihood to be exploited?**
We’re continuously drowning in CVEs — including many high-severity CVEs — but **the majority aren’t actually exploitable**. This, of course, can make it difficult to prioritize vulnerabilities as well as to estimate remediation efforts.
CVEs provide a “metric” for such exploitability (based on CVSS). **CVSS** scores vulnerabilities based on their characteristics and potential impacts but **don't consider real-world threat data**. Conversely, **EPSS** forecasts rely on up-to-the-minute **risk intelligence** from the CVE repository and **empirical data** about **real-world system attacks**.
While CVSS measures the inherent (theoretical) severity of vulnerabilities, EPSS predicts the likelihood of exploitation based on empirical data.
In this context, although Xygeni scores the severity of a CVE issue based on CVSS, the **Exploitability criteria adds a more reliable criteria to the funnel**, thus filtering out those issues with low exploitability likelihood.
{% hint style="info" %}
***Exploitability*** should be considered as a main criteria for **vulnerability prioritization** (see [Prioritization Funnels](/introduction-to-xygeni/prioritization-funnels.md))
{% endhint %}
You can view the EPSS Score associated with a vulnerability in the Vulnerability Details section.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.xygeni.io/introduction-to-xygeni/prioritization-funnels/prioritization-funnels-1/exploitability.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
