Skip to content
OpenAdvisories

Resources

Glossary

The terms you meet on this site — what they mean, where they come from and how we use them — and what the main security standards and regulations require about vulnerabilities.

Jump to: CVE · CNA · ADP · Alias · GHSA · EUVD · OSV · Security advisory · CSAF · PSIRT, CERT, CSIRT · CVSS · Severity rating · EPSS · SSVC · CWE · KEV · Exploited in the wild · Public exploit, PoC · Scanner template · Zero-day · Sightings · purl · CPE · Ecosystem · Affected range · Lockfile · SBOM · VEX · Malicious package · Backport · Source vs binary package · Low priority (distribution triage) · DSA, DLA, USN, RHSA … · Patch day · End of life (EOL) · LTS · Extended support · PCI DSS · CISA BOD 26-04 · EU Cyber Resilience Act · NIS2 · DORA · ISO/IEC 27001 · SOC 2 (and SAS 70)

Identifiers & records

CVE — Common Vulnerabilities and Exposures #
A public identifier for one vulnerability, such as CVE-2024-3400: the year it was reserved and a sequence number. CVE IDs are assigned by the CVE Program through CNAs. A CVE record holds a description, the affected products and versions, references and often scores; it does not say how to fix the problem in your setup. On this site: The CVE ID is the primary key: records from other databases are merged into it. How merging works.
CNA — CVE Numbering Authority #
An organisation allowed to assign CVE IDs and publish CVE records for its scope — usually a vendor for its own products (Microsoft, Red Hat, Siemens), an open-source foundation, a CERT or a bug-bounty platform. The CNA writes the first version of the record, including its own CVSS score where it gives one. On this site: The CNA's score is preferred as the headline score; patch-day pages count the CVEs a vendor published as CNA.
ADP — Authorized Data Publisher #
An organisation that adds data to CVE records written by others. CISA's ADP, Vulnrichment, adds CVSS scores, CWE weaknesses, KEV status and SSVC decision points to new CVEs that lack them. On this site: ADP scores fill in where the CNA gave none; SSVC decision points come from Vulnrichment.
Alias #
Another identifier for the same vulnerability in a different database, for example the GHSA and EUVD IDs of a CVE. On this site: Aliases are listed on the vulnerability page and searching by one finds the merged record.
GHSA — GitHub Security Advisory #
An identifier (GHSA-xxxx-xxxx-xxxx) in the GitHub Advisory Database, which covers open-source packages (npm, PyPI, Maven, Go, Composer …). Many GHSA records have a CVE as well; some do not.
EUVD — European Union Vulnerability Database #
The vulnerability database run by ENISA, the EU cybersecurity agency, under the NIS2 Directive. EUVD IDs look like EUVD-2025-12345; ENISA also flags vulnerabilities it knows to be exploited. On this site: ENISA EUVD section; ENISA's exploited flag counts as “exploited”.
OSV — Open Source Vulnerabilities #
A data format and a database (osv.dev) for vulnerabilities in open-source packages. An OSV record names the ecosystem, the package and exact affected version ranges, which makes it machine-checkable. GitHub, PyPA, Go, RustSec, Debian, Ubuntu, Alpine and others publish in it. On this site: The version check, lockfile, SBOM and server scans evaluate OSV ranges. Version matching.
Security advisory #
A document from a vendor, CERT or distribution announcing fixes for one or more vulnerabilities: affected products, fixed versions, workarounds. One advisory often covers many CVEs (a Red Hat RHSA, a Siemens SSA, a BSI WID bulletin). On this site: Advisories are kept as their own pages and linked to every CVE they cover.
CSAF — Common Security Advisory Framework #
An OASIS standard (version 2.0) for machine-readable security advisories in JSON, with a product tree and the status of each product per vulnerability. Used by BSI, Siemens, Red Hat, Cisco, CERT@VDE and others. On this site: Advisories from CSAF publishers are imported directly from their CSAF feeds.
PSIRT, CERT, CSIRT #
Teams that handle vulnerabilities. A PSIRT (Product Security Incident Response Team) handles vulnerabilities in its company's own products. A CERT or CSIRT (Computer Emergency / Security Incident Response Team) handles incidents and advisories for a country (BSI CERT-Bund, NCSC-NL), a sector or an organisation. On this site: Data sources lists the PSIRTs and CERTs we read.

Severity & prioritisation

CVSS — Common Vulnerability Scoring System #
A score from 0 to 10 for how severe a vulnerability is in itself, maintained by FIRST. The vector (for example CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) records how it was reached: attack vector, complexity, privileges and user interaction needed, and the impact on confidentiality, integrity and availability. The base score ignores whether anyone exploits it and how important the system is to you. CVSS 3.1 is the most common; CVSS 4.0 (2023) is replacing it. On this site: One headline score per vulnerability, all others listed below it. Which score is shown.
Severity rating #
The CVSS score in words: critical 9.0–10.0, high 7.0–8.9, medium 4.0–6.9, low 0.1–3.9. Advisories may use their publisher's own scale (BSI: kritisch / hoch / mittel / niedrig; Red Hat: Critical / Important / Moderate / Low). On this site: Critical vulnerabilities.
EPSS — Exploit Prediction Scoring System #
A daily probability, from FIRST, that a CVE will be exploited in the next 30 days, estimated from observed attack activity and the properties of the vulnerability. The percentile says how it ranks against all scored CVEs. EPSS is a prediction, not an observation: a CVE in KEV is exploited whatever its EPSS. On this site: Shown on each CVE page; Trending lists the largest EPSS increases of the week.
SSVC — Stakeholder-Specific Vulnerability Categorization #
A decision tree from CERT/CC, adopted by CISA, that gives an action instead of a score: Track, Track*, Attend or Act. CISA's model combines exploitation (none, public PoC, active), whether exploitation is automatable, the technical impact (partial or total control) and how important the affected system is (mission & well-being). On this site: Each CVE page shows the decision for low, medium and high importance. How it is computed.
CWE — Common Weakness Enumeration #
MITRE's catalogue of software weakness types — the kind of mistake behind a vulnerability, such as CWE-79 cross-site scripting or CWE-787 out-of-bounds write. A CVE is an instance; a CWE is its category. On this site: Weaknesses (CWE) lists vulnerabilities by weakness type.

Exploitation

KEV — Known Exploited Vulnerabilities catalog #
CISA's list of vulnerabilities with reliable evidence of exploitation in the wild, each with a required action and a remediation due date for US federal agencies, and whether ransomware groups are known to use it. Being in KEV is an observation, not a prediction. On this site: CISA KEV section; KEV and ENISA together make Exploited in the wild.
Exploited in the wild #
Attackers have been seen using the vulnerability against real systems. This is the strongest prioritisation signal there is. On this site: Marked when CISA KEV or ENISA EUVD says so; a vendor's own statement (Microsoft) is shown separately. Details.
Public exploit, PoC — Proof of concept #
Published code that triggers or exploits the vulnerability — a Metasploit module, an Exploit-DB entry, a GitHub repository. It is not proof of attacks, but it makes them cheap. Public PoCs are unreviewed and sometimes fake or malicious. On this site: Public exploit. Which sources count.
Scanner template #
A detection rule for an automated scanner — here, a Nuclei template — that checks whether a host is vulnerable. Not an exploit, but it lets anyone test the whole internet for the vulnerability with one command. On this site: Why it matters.
Zero-day #
A vulnerability exploited before, or at the moment, its fix is published — defenders had “zero days” to patch. Used loosely for any recently exploited bug; on this site it means exploited by the end of the patch-day window. On this site: Patch days count the zero-days of each Patch Tuesday.
Sightings #
Mentions of a vulnerability on social networks, blogs and feeds, counted by CIRCL Vulnerability-Lookup. They measure attention, not risk. On this site: Most discussed.

Packages, versions & SBOMs

purl — Package URL #
A standard way to name a package across ecosystems: pkg:npm/lodash@4.17.21, pkg:deb/debian/openssl@3.0.15-1~deb12u1?distro=debian-12. Used by SBOMs and OSV. On this site: SBOM scans check every component that has a purl.
CPE — Common Platform Enumeration #
NIST's naming scheme for products, such as cpe:2.3:a:apache:http_server:2.4.62:*:*:*:*:*:*:*, used by the NVD to say which products a CVE affects. Good for commercial products, poor for packages; purl is used for those.
Ecosystem #
A package world with its own registry and version rules: npm, PyPI, Maven, Go, crates.io, Packagist, NuGet, RubyGems, or a Linux distribution's packages. Version 1.10 sorts after 1.9 everywhere, but pre-releases, epochs and revisions differ. On this site: Version rules per ecosystem.
Affected range #
The versions a vulnerability affects, written as events: affected from introduced up to (not including) fixed, or up to and including last_affected. The fixed version is the first release without the vulnerability. On this site: Check a version evaluates these ranges.
Lockfile #
The file that pins the exact version of every direct and indirect dependency: package-lock.json, composer.lock, poetry.lock, go.sum. Manifests (package.json) only hold ranges, so they cannot be checked precisely. On this site: Scan a lockfile or SBOM.
SBOM — Software Bill of Materials #
An inventory of the components in an application or container image, with versions and identifiers. The two main formats are CycloneDX (OWASP) and SPDX (ISO/IEC 5962). Tools such as Syft and Trivy generate them. On this site: SBOM scan; how components are matched.
VEX — Vulnerability Exploitability eXchange #
A statement by a supplier on whether its product is actually affected by a vulnerability present in a component: not affected (with a justification, e.g. the vulnerable code is not used), affected, fixed or under investigation. Published in CSAF, CycloneDX or OpenVEX. On this site: Scans here do not read VEX documents yet; distribution triage plays a similar role for OS packages.
Malicious package #
A package published to a registry to attack whoever installs it — typosquats, hijacked maintainer accounts, dependency confusion. It is not a vulnerability with a fix: the only fix is removing it and rotating any secrets it could reach. On this site: Malicious packages; scans always flag them.

Linux distributions & patching

Backport #
Applying a fix to an older version instead of upgrading to the new upstream release. Distributions do this all the time, so a version like OpenSSL 3.0.7 on RHEL 9 can be fully patched. That is why Linux packages must be checked against the distribution's own fixed versions, not upstream ones. On this site: Linux distributions.
Source vs binary package #
Debian and Ubuntu build several binary packages (libssl3, openssl) from one source package (openssl). Advisories are written per source package. On this site: Server scans report by source package.
Low priority (distribution triage) #
CVEs a distribution has assessed and does not plan to fix with a security update: Debian unimportant, no-DSA, postponed, ignored; Ubuntu negligible. Often the vulnerable code or configuration is not present in that distribution. On this site: Listed separately in server scans, never mixed with what needs attention. Details.
DSA, DLA, USN, RHSA … #
Distribution advisory IDs: Debian Security Advisory (DSA) and Debian LTS Advisory (DLA), Ubuntu Security Notice (USN), Red Hat Security Advisory (RHSA), SUSE-SU, Rocky RLSA, AlmaLinux ALSA, Amazon ALAS, Oracle ELSA.
Patch day #
A vendor's fixed release date for security fixes: Microsoft's Patch Tuesday (second Tuesday of the month), shared by Adobe, SAP, Siemens and others; Oracle's quarterly Critical Patch Update; the monthly Android bulletin. A fix outside the schedule is out-of-band. On this site: Patch days.

Support & lifecycle

End of life (EOL) #
The date after which a release gets no more security fixes. New vulnerabilities in it stay unfixed, whether or not any are known today. On this site: Support & end of life for every tracked product.
LTS — Long-term support #
A release line maintained for longer than usual, typically several years, often with security fixes only after the first period.
Extended support #
Security fixes after the regular end of life, often paid or from a separate team: Ubuntu Pro (ESM), Debian LTS and ELTS, RHEL ELS. Package versions then come from that programme, not the regular archive. On this site: How support is reported in scans.

Standards & regulations: what they require about vulnerabilities

Only the vulnerability-management part of each — not a summary of the whole standard. These are plain-language summaries for orientation, not legal or audit advice; the official text decides.

PCI DSS #

Payment Card Industry Data Security Standard — current version 4.0.1

Required of every organisation that stores, processes or transmits payment card data; set by the PCI Security Standards Council. Version 4.0.1 (June 2024) replaced 4.0, which was retired on 31 December 2024.

About vulnerabilities

  • Identify security vulnerabilities from industry sources and rank them by risk (requirement 6.3.1).
  • Install patches for critical vulnerabilities within one month of release; other patches within a time frame set by your own risk assessment (6.3.3). Version 4.0.1 went back to “critical” only — 4.0 had said “critical or high”.
  • Run internal vulnerability scans at least every three months (11.3.1) and external scans by an Approved Scanning Vendor (ASV) every three months (11.3.2).

What helps here: Severity and exploitation status per CVE for the risk ranking; server and dependency scans between the quarterly scans. Official source: PCI SSC.

CISA BOD 26-04 #

Binding Operational Directive 26-04, “Prioritizing Security Updates Based on Risk” (June 2026)

Binding for US federal civilian executive-branch agencies; widely used as a reference elsewhere. It replaced BOD 22-01 (2021), which had set fixed deadlines for KEV entries: six months for CVEs from before 2021, two weeks for all others.

About vulnerabilities

  • Remediation deadlines, in calendar days, follow a table informed by SSVC, with four decision points: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact.
  • The clock starts when CISA adds the CVE to KEV or when the agency finds it on its own assets, whichever is first.
  • Agencies must update their vulnerability-management policies within 60 days and remediate according to the table within 180 days of issuance.

What helps here: KEV status, and the SSVC automatable / technical-impact points from CISA Vulnrichment, are shown on every CVE page; whether an asset is exposed only you know. Official source: CISA.

EU Cyber Resilience Act #

Regulation (EU) 2024/2847

Cybersecurity requirements for products with digital elements — hardware and software — placed on the EU market. In force since 10 December 2024; the reporting obligations apply from 11 September 2026, the main obligations from 11 December 2027.

About vulnerabilities

  • Manufacturers must report actively exploited vulnerabilities in their products: an early warning within 24 hours, a notification within 72 hours and a final report within 14 days after a fix or mitigation is available.
  • Reports go to the national CSIRT and to ENISA, once, through ENISA's Single Reporting Platform.
  • Manufacturers must handle vulnerabilities and provide security updates throughout a support period whose end date is stated at the time of purchase.

What helps here: Exploitation status from CISA KEV, ENISA and vendors; SBOM scans for the components in your product; EOL data for the components you depend on. Official source: European Commission.

NIS2 #

Directive (EU) 2022/2555

EU directive on cybersecurity for essential and important entities in sectors such as energy, transport, health, digital infrastructure and public administration. Member States had to transpose it into national law by 17 October 2024; the obligations come from those national laws.

About vulnerabilities

  • Cybersecurity risk-management measures include security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure (Article 21).
  • Significant incidents are reported in stages: an early warning within 24 hours, a notification within 72 hours, a final report within one month (Article 23).
  • It created coordinated vulnerability disclosure in every Member State and the European vulnerability database run by ENISA — the EUVD (Article 12).

What helps here: EUVD records and ENISA's exploited flag are merged into every CVE; server scans cover vulnerability handling on Linux systems. Official source: European Commission.

DORA #

Digital Operational Resilience Act, Regulation (EU) 2022/2554

ICT risk management for EU financial entities — banks, insurers, investment firms, payment institutions — and their critical ICT providers. It has applied since 17 January 2025.

About vulnerabilities

  • An ICT risk-management framework that includes vulnerability and patch management, detailed in the regulatory technical standards on ICT risk management (Delegated Regulation (EU) 2024/1774).
  • Digital operational resilience testing, including vulnerability assessments and scans; threat-led penetration testing for the largest entities.

What helps here: Vulnerability data and scans for the patch-management process; feeds and daily notifications to follow vendors you depend on. Official source: EIOPA.

ISO/IEC 27001 #

Information security management systems — 2022 edition

The international standard for an information security management system (ISMS), certified by accredited bodies. Annex A lists 93 controls; certificates to the 2013 edition had to move to 2022.

About vulnerabilities

  • Control 8.8, Management of technical vulnerabilities: obtain information about technical vulnerabilities of the systems in use, evaluate your exposure and take appropriate measures.
  • Related controls cover the asset inventory (5.9), configuration management (8.9) and secure development (8.25–8.28).

What helps here: Sources of vulnerability information (feeds, notifications, API) and evidence of evaluation (scan reports). Official source: ISO.

SOC 2 (and SAS 70) #

System and Organization Controls reports, AICPA

Audit reports on a service organisation's controls, issued by a CPA firm. SOC 1 covers controls relevant to customers' financial reporting; SOC 2 covers the Trust Services Criteria (security, availability, processing integrity, confidentiality, privacy). A Type I report assesses the design at a point in time, a Type II report whether controls worked over a period. SAS 70, the older US standard for such audits, was replaced by SSAE 16 in 2011 and then by SSAE 18 in 2017; a “SAS 70 report” no longer exists.

About vulnerabilities

  • The security criteria expect the organisation to detect and monitor for newly discovered vulnerabilities and for configuration changes that introduce them (common criterion CC7.1), and to evaluate and respond to them.

What helps here: Evidence of ongoing monitoring: notifications, scan reports, CI checks that fail on new vulnerabilities. Official source: AICPA.

Missing a term, or found a mistake? Tell us.