← CRA Glossary
CVD & Vulnerability Management

Vulnerability Triage

Vulnerability triage is the process of evaluating incoming vulnerability reports or newly disclosed CVEs to determine their validity, severity, applicability to specific products, and remediation priority. Effective triage is essential for CRA compliance, ensuring that critical vulnerabilities are addressed within required timeframes.

Vulnerability triage is the process of evaluating incoming vulnerability reports or newly disclosed CVEs to determine their validity, severity, applicability to specific products, and remediation priority. Effective triage is essential for CRA compliance, ensuring that critical vulnerabilities are addressed within required timeframes.

CVD & Vulnerability Management

Last updated 19 July 2026

What Is Vulnerability Triage?

Vulnerability triage is the structured process of evaluating a vulnerability - whether received through a researcher report, a CVE disclosure, or an automated scanner alert - to determine whether it is valid, which products or components it affects, how severe it is in context, and what priority to assign to remediation. The term borrows from medical triage: just as hospitals prioritise patients by urgency, security teams prioritise vulnerabilities by exploitability, impact, and remediation complexity. Without a triage process, high volumes of vulnerability reports overwhelm engineering teams and cause genuinely critical issues to be missed among routine low-severity findings. The CRA requires manufacturers to address vulnerabilities 'without undue delay' - meaningful only if they can first determine which vulnerabilities require what level of urgency.

CRA reference:Article 13

The Triage Process: Validation, Scoring, and Prioritisation

A complete triage workflow involves three stages:

Validation: Confirming the reported vulnerability is genuine and reproducible. For researcher reports, this means setting up a test environment and reproducing the issue. For CVE-based alerts (e.g., a new CVE in a library in the SBOM), this means confirming whether the vulnerable code path is actually reachable in the product.

Scoring: Assigning a severity score using CVSS (v3.1 or v4.0) and optionally supplementing with EPSS for exploitation likelihood. The product's threat context affects the Environmental Score - a vulnerability that is critical in isolation may be lower severity when compensating controls are applied.

Prioritisation: Ranking the validated, scored vulnerabilities against available remediation capacity. Prioritisation considers: CVSS score, EPSS score, whether the vulnerability is in the CISA KEV catalogue, potential harm to users, and complexity of the fix.

CRA reference:Article 13, Annex I

Triage in the Context of CRA Obligations

The CRA's Article 14 requires manufacturers to notify ENISA of actively exploited vulnerabilities within 24 hours. This notification obligation cannot be met unless the manufacturer has a triage process capable of making a rapid determination of exploitation status. Similarly, the general obligation to address vulnerabilities 'without undue delay' requires a triage outcome - severity and remediation priority - to be established promptly after a vulnerability is identified. PSIRT teams responsible for CRA compliance should have documented triage SLAs: for example, all researcher reports acknowledged within 5 business days, initial severity assessment within 10 business days, and exploited vulnerabilities triaged within hours rather than days. These SLAs should be tracked and auditable.

CRA reference:Article 13, Article 14

Tooling for Vulnerability Triage

Manual triage is unsustainable for products with large dependency trees. Modern triage tooling includes:

  • SBOM-driven correlation: Automated matching of new CVEs against the product's SBOM to surface only relevant vulnerabilities, filtering out the large proportion of NVD/CVE entries that do not affect the specific components in the product.
  • VEX documents: Vendor statements (Vulnerability Exploitability eXchange) asserting that specific CVEs do not affect a product version, enabling downstream users to filter noise.
  • EPSS integration: Incorporating EPSS scores into automated prioritisation to focus on vulnerabilities most likely to be exploited, not just those with high CVSS scores.
  • PSIRT ticketing systems: Structured case management tracking each vulnerability from intake through triage, remediation, and advisory publication.

CVD Portal integrates SBOM-driven CVE correlation and VEX generation to automate significant portions of the triage workflow.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

How should triage handle a CVSS 9.8 vulnerability in a dependency that the product doesn't actually call?+

If a high-CVSS vulnerability exists in a component that is present in the product's SBOM but the vulnerable code path is provably unreachable in the product's implementation, the vulnerability's practical risk to the product is low. The manufacturer should document this analysis in a VEX document - specifically a 'not affected' assertion - which allows users and downstream operators to deprioritise patching in their environments while the manufacturer prepares an update. This documented analysis is important: MSAs may ask for evidence of how high-severity CVEs were assessed.

What is a reasonable triage SLA for CRA purposes?+

The CRA requires that actively exploited vulnerabilities be reported to ENISA within 24 hours of the manufacturer becoming aware. This means exploited vulnerabilities must be triaged (at least to the level of confirming exploitation status) within hours of being identified. For non-exploited researcher reports, ENISA's CVD Good Practice Guide suggests acknowledgement within 5 business days and initial triage within 10-15 business days. Critical severity vulnerabilities (CVSS 9.0+) should be triaged and assessed within 5 business days. Manufacturers should codify their triage SLAs in their PSIRT policy.

Does triage apply to vulnerabilities reported through automated scanning tools, not just researcher reports?+

Yes. The CRA's vulnerability handling obligations apply regardless of the source of vulnerability information - researcher reports, automated SAST/DAST scanning, SBOM-based CVE correlation, penetration test findings, or intelligence feeds. All identified vulnerabilities must go through a documented triage process. Scanner-generated findings are especially likely to include false positives and low-severity issues, making a rigorous validation step in triage even more important for scanner-sourced findings.

Sector checklists covering Vulnerability Triage

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Vulnerability Triage fits into your complete CRA compliance programme.

View checklists →