Repository navigation
vcio-api-v3: Store exploits and EPSS based on new advisory models #2069
Description
Currently, we store exploits in AdvisoryExploits and associate them with other advisories. If we can find any related identifier in aliases or advisory_id of any Advisory.
For example:
we have exploits with CVE-1234 as an identifier. We will relate that exploit to all advisories that have that identifier either as it's alias or advisory ID
Shall we store exploits as an advisory of it's own or shall we relate exploits to other advisories like we are doing currently?
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
DennisClark commentedon Dec 19, 2025
@TG1999 I think
we relate exploits to other advisories like we are doing currentlymakes the most sense, since I think we need to be clear about the distinction between advisories and exploits.[-]Plan storing of exploits based advisories[/-][+]Plan storing of exploits and EPSS based advisories[/+]TG1999 commentedon Feb 17, 2026
This is done now
Reference:
[-]Plan storing of exploits and EPSS based advisories[/-][+]vcio-api-v3:Plan storing of exploits and EPSS based advisories[/+][-]vcio-api-v3:Plan storing of exploits and EPSS based advisories[/-][+]vcio-api-v3: Plan storing of exploits and EPSS based advisories[/+][-]vcio-api-v3: Plan storing of exploits and EPSS based advisories[/-][+]vcio-api-v3: Store exploits and EPSS based on new advisory models[/+]