CRA vulnerability handling requirements: what Annex I Part II asks of manufacturers

Under the Cyber Resilience Act, vulnerability handling is a continuing manufacturer obligation, not a product feature: Annex I Part II requires an SBOM, remediation of vulnerabilities without delay, regular security testing, public advisories for fixed vulnerabilities, a coordinated vulnerability disclosure policy, a contact point, secure and timely distribution of updates and, where possible, free security updates for the support period. Article 14 adds the reporting duty for actively exploited vulnerabilities.

By the Vellaci teamPublished Updated 5 min readOperational guidance, not legal advice

Share:LinkedInXE-mail

Key facts

Where
Annex I Part II (1)–(8); Article 13(6)–(8); Article 14 for reporting
Since when
Reporting since 11 September 2026; the essential requirements apply from 11 December 2027 (products already on the market only if substantially modified)
Duration
For the support period of each product — at least five years unless the expected use is shorter
Evidence
SBOM per version, triage decisions with reasons, test reports, advisories, disclosure policy, update logs

The problem this solves

Most manufacturers already receive vulnerability information — scanner alerts, researcher e-mails, upstream advisories — but rarely as a process with owners, deadlines and evidence. The CRA turns that informal flow into an obligation with two hard edges: vulnerabilities in shipped products must be handled and remediated without delay, and actively exploited ones must be reported within 24 hours of awareness. A team that cannot answer 'which products on the market contain this component, who decided what, and when' cannot meet either.

What Annex I Part II requires

RequirementWhat it means operationallyEvidence to keep
(1) Identify and document vulnerabilities and components, including an SBOMAn SBOM in a machine-readable format covering at least the top-level dependencies, per product versionSBOM files with checksums, bound to versions
(2) Address and remediate vulnerabilities without delay, including security updatesTriage with an owner and a decision; fixed releases; workarounds where fixes are not yet availableDecision history per finding, release notes, fixed-version links
(3) Apply effective and regular tests and reviewsSecurity testing per release and periodic reviews of the product's securityTest reports with scope, date and findings
(4) Publicly disclose fixed vulnerabilitiesAdvisories once a security update is available, describing the vulnerability, the affected versions and the fixAdvisory archive with dates
(5) Put in place and enforce a coordinated vulnerability disclosure policyA published policy with a contact, scope, handling commitments and safe-harbour languagePolicy versions; security.txt
(6) Facilitate sharing of information, including a contact addressA working intake channel that acknowledges and handles reportsIntake log with response times
(7) Distribute updates securely and in a timely mannerSigned update mechanisms; distribution that reaches the installed baseUpdate mechanism description, signing procedures, rollout records
(8) Provide security updates without delay and free of charge, with advisoriesSeparate security updates from feature updates where possible; no charge during the support periodRelease policy, update logs

One operational workflow

The eight requirements are easier to run as one chain than as eight controls. The chain starts at the release pipeline and ends at an evidence record:

  1. Generate an SBOM for every supported version in the build that produces the artefact; store it with its checksum against the version.
  2. Match every component continuously against advisory sources (OSV, GitHub advisories) and enrich with exploitation evidence (CISA KEV, EPSS) so the queue is ranked by exploitation, not alphabet.
  3. Triage each finding with a named reviewer, an explicit state (affected, not affected, fixed, workaround, risk accepted) and a written reason; assign remediation with a due date derived from severity and exploitation.
  4. Ask the Article 14 question explicitly on every affected finding: not reviewed, potentially reportable, confirmed reportable, not reportable — with the awareness time recorded when exploitation is confirmed.
  5. Ship the fix as a security update; link the fixed release to the finding; publish the advisory; issue a VEX statement for components that were not exploitable.
  6. Keep the disclosure policy, security.txt and intake mailbox operating, with acknowledgement and handling commitments met and logged.
  7. File the evidence as it is produced — SBOMs, decisions, test reports, advisories, update logs — against the product and the requirement it satisfies.

Common mistakes

  • Treating scanner output as the process: alerts without owners, reasons and deadlines do not evidence 'without delay'.
  • SBOMs generated on request rather than per release, so exposure cannot be answered for the versions customers run.
  • No written awareness rule, so nobody can say when the 24-hour clock started.
  • Advisories published only for headline CVEs, leaving the archive incomplete.
  • A disclosure policy on the website with no one reading the mailbox.

What Vellaci does — and what it leaves to you

Vellaci is the system of record for this chain: SBOM ingestion per version from CI, the API or the GitHub App; continuous matching against OSV, GitHub advisories, KEV and EPSS with source provenance; a triage workflow with mandatory reasons, remediation ownership and an explicit CRA review; VEX statements; fixed-release links; a disclosure policy and security.txt workspace; and an evidence vault with an append-only audit log. It keeps your scanner, tracker and pipeline; it does not replace them. Reachability, risk acceptance and reportability remain decisions made by named people in your organisation — Vellaci records who decided, why and when.

Where to start

The free assessment on this site asks how vulnerabilities in third-party components are handled today, whether an SBOM exists per release, how disclosure reports arrive and whether the reporting workflow has been rehearsed, and returns a banded gap map with the evidence each gap would need. Most teams start with the SBOM pipeline and the triage workflow, because everything else — reporting, advisories, updates — depends on knowing what is in the product.

Frequently asked questions

Does every vulnerability in an SBOM have to be fixed?
No. The obligation is to handle and remediate vulnerabilities that affect the product without delay. A component that is present but not exploitable in your product can be documented as not affected — ideally as a VEX statement with the reason — and that decision is itself evidence of handling.
Do we have to publish an SBOM?
The CRA requires the SBOM to be documented and available to market surveillance authorities on request; it does not require publication. Customers increasingly ask for it in procurement, and sharing per version is good practice.
What counts as 'without delay'?
The regulation does not fix a number of days. A defensible practice is a written SLA by severity and exploitation status, evidence that it is met, and documented reasons when it is not. Actively exploited vulnerabilities have the separate 24-hour reporting duty under Article 14.
How is this different from Article 14 reporting?
Annex I Part II is the continuous handling process for all vulnerabilities in the product; Article 14 is the notification duty to ENISA for the subset that is actively exploited (and for severe incidents). A good handling process is what makes the reporting duty meetable.

From requirement to evidence

What the obligations in this guide mean for an engineering, security or compliance team, the Vellaci workflow that supports each one, and the records it leaves. The full map for every CRA obligation is on the CRA compliance software page.

How to read this. Official requirement summarises the text of Regulation (EU) 2024/2847 with its reference. What your team does is Vellaci’s operational interpretation, not legal advice. Vellaci workflow and Evidence describe what the product does today. Methodology · reviewed 2026-10-05.

  1. Software bill of materials

    Annex I, Part II(1)Applies from 11 Dec 2027
    Official requirement
    Identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies.
    What your team does (interpretation)
    Generate an SBOM in the build for every released version, keep it with that version rather than overwriting it, and make sure components carry identifiers (purls) that vulnerability data can be matched against.
    Vellaci workflow
    SBOM ingestion per product version (UI, API, CLI, GitHub/GitLab), original file preserved, components normalised and deduplicated. How it works
    Evidence produced
    • Original SBOM file with SHA-256 checksum, bound to the version
    • Parse record and warnings
    • Component inventory per version and diff against the previous version
  2. Address and remediate without delay

    Annex I, Part II(2)Applies from 11 Dec 2027
    Official requirement
    In relation to the risks posed, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, provide security updates separately from functionality updates.
    What your team does (interpretation)
    Every matched vulnerability gets a human decision — affected, not affected, fixed, accepted — with a reason, an owner and, if affected, a remediation target and the version that fixes it.
    Vellaci workflow
    Triage with mandatory reasons, explainable priority (CVSS, EPSS, KEV, exposure), remediation owner and due date, Jira and Linear ticket links. How it works
    Evidence produced
    • Decision history per finding with reviewer and timestamp
    • Remediation owner, due date and fixed version
    • Linked tickets
  3. Systematically document vulnerabilities

    Article 13(7)Applies from 11 Dec 2027
    Official requirement
    Systematically document, proportionately to the nature and the cybersecurity risks, relevant cybersecurity aspects of the product, including vulnerabilities the manufacturer becomes aware of and relevant information provided by third parties, and update the risk assessment where applicable.
    What your team does (interpretation)
    Keep the reasoning, not just the status. A 'not affected' without a justification is not documentation; neither is a status that was silently overwritten.
    Vellaci workflow
    Append-only decision history and hash-chained audit log; VEX states with CycloneDX justification codes per product version. How it works
    Evidence produced
    • Per-product VEX statements with justification
    • Audit log entries with before and after values
    • CycloneDX VEX export per version
  4. Disclose fixed vulnerabilities

    Annex I, Part II(4)Applies from 11 Dec 2027
    Official requirement
    Once a security update has been made available, share and publicly disclose information about fixed vulnerabilities, including a description, the affected products, impact, severity and information helping users remediate; publication may be delayed in duly justified cases.
    What your team does (interpretation)
    Tie each advisory to the finding and the fix release, and record when and where it was published — or why publication was delayed.
    Vellaci workflow
    Fixed versions recorded on findings; CycloneDX VEX export for customers and downstream integrators. How it works
    Evidence produced
    • Fixed version linked to the finding
    • Exported VEX document
    • Publication or delay rationale
  5. Effective and regular security tests

    Annex I, Part II(3)Applies from 11 Dec 2027
    Official requirement
    Apply effective and regular tests and reviews of the security of the product.
    What your team does (interpretation)
    Decide which tests run per release and per period (SAST, dependency scanning, penetration tests, reviews), and keep the reports where an assessor can find them per product.
    Vellaci workflow
    Test reports attached to products and requirements in the evidence vault, with review dates; readiness controls show which are missing or overdue. How it works
    Evidence produced
    • Test reports linked to the product, with checksum and review date
    • Readiness control status per requirement
  6. Secure, timely and free security updates

    Annex I, Part II(7)–(8)Applies from 11 Dec 2027
    Official requirement
    Provide mechanisms to securely distribute updates so vulnerabilities are fixed or mitigated in a timely manner — automatically where applicable — and disseminate available security updates without delay and, unless otherwise agreed for a tailor-made product, free of charge, with advisory messages.
    What your team does (interpretation)
    Document how updates are signed, delivered and applied per product, and be able to show which release fixed which vulnerability and when it was made available.
    Vellaci workflow
    Secure update mechanism section per product in the technical documentation; fixed versions recorded on findings. How it works
    Evidence produced
    • Update mechanism description with version history
    • Finding → fixed version → release date
  7. Coordinated vulnerability disclosure and contact address

    Annex I, Part II(5)–(6)Applies from 11 Dec 2027
    Official requirement
    Put in place and enforce a policy on coordinated vulnerability disclosure, and facilitate the sharing of information about potential vulnerabilities, including by providing a contact address for reporting them.
    What your team does (interpretation)
    Publish a reachable intake channel (for example security.txt), a disclosure policy with response targets, and keep a record of reports received and how they were handled.
    Vellaci workflow
    CVD settings per organisation: vulnerability contact, reporting URL, security.txt status, published policy URL, intake instructions and acknowledge / triage / fix targets; policy template aligned with ISO/IEC 29147. How it works
    Evidence produced
    • Recorded contact point, security.txt and policy URL
    • Response targets (acknowledge, triage, fix)
    • Changes to the settings in the audit log
  8. Report actively exploited vulnerabilities

    Article 14(1)–(2)Applies since 11 Sep 2026
    Official requirement
    Notify any actively exploited vulnerability contained in the product to the CSIRT designated as coordinator and to ENISA via the single reporting platform: early warning within 24 hours of becoming aware, notification within 72 hours, final report no later than 14 days after a corrective or mitigating measure is available.
    What your team does (interpretation)
    Decide who confirms awareness and reportability, record when they did it and in which timezone, and have the content of each stage ready before the clock runs out.
    Vellaci workflow
    Explicit CRA review on every finding, reporting case with server-computed 24 h / 72 h / final-report deadlines, staged and prefilled forms. How it works
    Evidence produced
    • Reportability decision with rationale and reviewer
    • Confirmed awareness time and timezone
    • Frozen revision of each submitted stage with SRP reference

Run vulnerability handling as one workflow.

SBOM per version, continuous matching with KEV and EPSS, triage with reasons, VEX and an explicit CRA review — with the evidence filed as you go.