> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/sbom360/projects/vulnerabilities.md).
# Vulnerabilities
### What is Vulnerability?
A security flaw, glitch, or weakness found in software code that could be exploited by an attacker (threat source).
To understand the overall risk of a software, it is important to understand the vulnerabilities of the direct as well as the transitive dependencies.
### Understanding Vulnerabilities
* Count of components that are vulnerable is displayed towards left, along with the category of the components (open-source, private, third-party, unknown).
* The vulnerability count is displayed towards the right, grouped by severity (critical, high, medium, low).
* Each tile is clickable which will list down the components applicable to that filter in a table view. The details will list the component name, version, total vulnerabilities and a capsule for vulnerabilities details.
* By clicking the vulnerabilities capsule, next level details will be shown as below.
* By clicking on any row, the sidesheet shows up as shown below.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.veedna.com/sbom360/projects/vulnerabilities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.