Skip to content

Vulnerability sources

Affectra matches the components of your releases against public vulnerability data. It keeps its own copy of every source below and matches against that copy, so your component lists never leave Affectra. See How matching works.

Source What Affectra takes from it How it is used
OSV, one data set per ecosystem Advisories and the package versions they affect: Debian, Ubuntu, Alpine, npm, Go, crates.io, PyPI, Maven, RubyGems, NuGet and Packagist. Matches components by package URL. Affectra reads only the data sets that some component needs.
NVD CVEs, their CVSS scores and severities, and the CPE names they affect. Gives the severity and CVSS score of a finding. Matches components by CPE.
CISA KEV The catalog of vulnerabilities known to be exploited. Marks a finding Known exploited.
ENISA EU KEV ENISA’s list of vulnerabilities known to be exploited, from the EU Vulnerability Database. It includes CISA’s catalog and adds entries from other sources. Marks a finding Known exploited for the entries from sources other than CISA. For CISA’s entries, CISA’s own catalog decides, so a CVE that CISA removes isn’t kept known exploited by ENISA’s copy.
ENISA EUVD The EUVD ID of each CVE, such as EUVD-2025-4893, from ENISA’s EU Vulnerability Database. Only the IDs and the CVEs they stand for; scores still come from the NVD. Shows a finding’s EUVD IDs, each linking to its page in the EUVD, and adds them to the CSAF VEX export and to the agent tools.
CSAF providers: BSI CERT-Bund WID, CERT@VDE, Phoenix Contact, CISA, Siemens The security advisories of vendors and coordinators, as signed CSAF 2.0 documents. Each provider is off until its terms are reviewed. Shows the Vendor advisories that name a finding’s CVEs, with fixed versions and links. See Vendor advisories.
FIRST EPSS The probability that a CVE is exploited in the next 30 days. Shows the EPSS score of a finding.
MITRE CWE, CAPEC and ATT&CK Catalogs of weaknesses, attack patterns and attack techniques. Context for vulnerabilities.

The two KEV lists, the EUVD IDs, the vendor advisories, EPSS and the MITRE catalogs only add context. They never create a finding and never remove one. They show on existing findings as soon as their source has refreshed. The timeline under a finding’s Details says which list marks it known exploited.

Affectra reads the NVD. If it ever can’t, CPE matches and CVSS scores are missing, and the release says so: CVSS scores are unavailable: NVD sync is off.

MITRE’s catalogs, ENISA’s data and the CSAF providers’ advisories come with licence and copyright notices. See Licences and notices.

Choose vulnerability feeds explains how to do it in Settings, and what it changes.

An admin or owner can turn NVD, and each CSAF provider, off for your organization. Findings that only that feed reports then disappear from lists, counts, exports, the graph and the agent tools, for your organization only. Nothing is deleted: when the feed is turned on again, its findings come back. Turning a feed off sends no finding.resolved, and turning it back on sends no finding.new for findings that were there before. OSV and the feeds that only add context (both KEV lists, the EUVD IDs, EPSS and the MITRE catalogs) are always on.

Every feed is on until someone turns it off. A CSAF VEX export lists the feeds your organization has turned off in its notes, and a release’s data freshness leaves them out. Affectra staff see which feeds your organization has turned off, so support can tell why a finding is missing, but they can’t change them.

The API lists the feeds, with their state and who last changed them, at GET /v1/orgs/{org}/feeds, and turns one off with PUT /v1/orgs/{org}/feeds/{feed} and the body {"subscribed": false} ({"subscribed": true} turns it on again). The feed is nvd, or csaf: and the provider, such as csaf:siemens. Each change is an org.feed_subscription_changed event in the events feed and for webhooks that select it.

Affectra checks OSV, NVD, both KEV lists and EPSS every 6 hours by default. It checks again when the last attempt is 6 hours old, whether that attempt changed anything or not. A check that fails is tried again after the same time.

The MITRE catalogs change rarely, so Affectra checks them once a week.

The EUVD has no download of the whole database, so Affectra reads it page by page: once a week all of it, spread over several checks, and every 6 hours in between only the records that changed. An installation can turn the EUVD off; its findings then have no EUVD IDs, and the release doesn’t list the EUVD as a source.

Each CSAF provider an installation turns on is checked every 6 hours too. Its first check reads all of its advisories, which can take an hour or more for a large provider; the other sources don’t wait for it.

When OSV or NVD data has changed, Affectra matches the components again. A new upload is matched within seconds, and if it needs an OSV data set that Affectra has not loaded yet, that data set is fetched shortly after the upload.

A source is stale when its last successful check is older than the threshold in the table, and very stale when it is older than the second one. A check that found nothing new still counts. The release warns you, on the Vulnerabilities tab, that results may be incomplete while a source is stale, or when a source was never loaded.

Source Stale after Very stale after
OSV, each data set 13 hours 24 hours
NVD 24 hours 48 hours
CISA KEV 13 hours 24 hours
ENISA EU KEV 13 hours 24 hours
ENISA EUVD 24 hours 48 hours
FIRST EPSS 48 hours 96 hours
Each CSAF provider 13 hours 24 hours
MITRE CWE, CAPEC and ATT&CK 15 days 30 days

EPSS is published once a day, so it gets two missed days. The MITRE catalogs and the CSAF providers are not part of the freshness line of a release, because findings do not depend on them.

The Vulnerabilities tab of a release shows when its components were last checked and against which sources, with each source’s last check and last change under Details. Assess findings with VEX describes the tab. The API gives the same data at GET /v1/orgs/{org}/releases/{release}/data-freshness.