EU Cyber Resilience Act: SBOM and reporting duties for products that ship ML models
The CRA's reporting clock is already running, and its SBOM duty follows in December 2027. If your product ships model weights, those files are components like any other, and a pickle-based checkpoint is code that runs when it loads.
Who it applies to
The CRA binds manufacturers of products with digital elements made available on the EU market. Article 3(1) covers software and hardware products, including components placed on the market separately. Article 3(13) makes you the manufacturer if you develop such a product, or have it developed, and market it under your own name, "whether for payment, monetisation or free of charge".
Products placed on the market before 11 December 2027 fall under the CRA only if they are substantially modified after that date (Article 69(2)). The exception is Article 14 reporting, which Article 69(3) applies to them anyway.
Key dates
- 11 Jun 2026
- Rules on conformity assessment bodies apply (Chapter IV, Article 71(2)).
- 11 Sep 2026
- Article 14 reporting of actively exploited vulnerabilities and severe incidents applies (Article 71(2)).
- 11 Dec 2027
- The rest of the Regulation applies, including the Annex I essential requirements and the SBOM in Annex I Part II(1) (Article 71(2)).
Breaching Annex I or Articles 13 and 14 can draw fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher (Article 64(2)). Member States set and enforce penalties.
What the text asks for
Reporting (Article 14, in force)
- An early warning of an actively exploited vulnerability within 24 hours of becoming aware of it.
- A vulnerability notification within 72 hours, with corrective or mitigating measures.
- A final report no later than 14 days after a corrective or mitigating measure is available.
Notifications go simultaneously to the CSIRT designated as coordinator and to ENISA, through the single reporting platform (Article 14(1)). Severe incidents follow a parallel 24-hour / 72-hour / one-month track (Article 14(3)-(4)). You cannot report a vulnerability in a component you don't know you ship.
Vulnerability handling (Annex I Part II, from 11 December 2027)
- Point (1): identify and document vulnerabilities and components, "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".
- Point (2): address and remediate vulnerabilities without delay, including through security updates.
- Article 13(5): exercise due diligence when integrating third-party components, open-source ones included.
The SBOM is part of the technical documentation in Annex VII. You are not required to publish it. Article 13(24) lets the Commission set the SBOM's format and elements by implementing act, so check for one before you fix a format.
Where an AI BOM helps, and where it doesn't
AIsbom produces a CycloneDX 1.7 or SPDX JSON document for the ML side of a product: model files and the Python
dependencies pinned in requirements.txt. It does not inventory npm packages, OS packages or
container layers, so pair it with your general-purpose SBOM tool. The right-hand column is our reading of the
overlap, not the regulation's.
| CRA provision | What AIsbom records | Coverage |
|---|---|---|
| Annex I Part II(1): machine-readable SBOM, top-level dependencies | CycloneDX 1.7 (or 1.6 / 1.5) and SPDX 2.3 / 3.0 JSON listing model files and pinned Python packages | The ML portion of the product. Other ecosystems need another tool. |
| Annex I Part II(1): identify vulnerabilities in components |
Pickle opcode analysis for dangerous imports in model files; with --vex, OSV lookups for
CVEs affecting exact requirements.txt pins
|
Yes for those two sources. Unpinned dependencies can't be matched. |
| Annex I Part II(2): address and remediate vulnerabilities |
OpenVEX or CycloneDX VEX stating whether each finding affects the scanned artifact; findings that
disappear against a baseline are marked fixed
|
Records the status. The remediation and the security update are yours. |
| Article 13(5): due diligence on third-party components | SHA-256 per model file, declared licence, malware findings for models pulled from Hugging Face | Evidence for one part of due diligence on third-party models. |
| Article 14: 24-hour early warning | On the platform, an alert when a new AIsbom advisory matches a component in a connected repo | Helps you notice. AIsbom does not notify ENISA or any CSIRT for you. |
Generating the evidence
pip install aisbom-cli
# SBOM plus VEX for the ML side of the product (writes sbom.openvex.json and sbom.vex.cdx.json)
aisbom scan . --output sbom.json --vex
# Mark findings that disappeared since the last release as fixed
aisbom scan . --output sbom.json --vex --vex-baseline last-release-sbom.json
# Detect drift in models, hashes and licences between two releases
aisbom diff last-release-sbom.json sbom.json
To run this on every pull request, use the AIsbom GitHub Action and connect the repository to the platform, which keeps the history.
See which CRA evidence your repo is missing
The readiness view breaks your latest scan down by component identity, integrity, licences and exploitability statements, and lists each gap with the provision it maps to. Free on every plan.
Open the readiness view Other regulationsSources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Official Journal: Articles 3, 13, 14, 64, 69, 71 and Annexes I, II and VII.
Last reviewed 2026-10-31 against the Official Journal text. This page is general information, not legal advice. AIsbom reports what an SBOM contains. It does not assess or attest to anyone's regulatory status, does not file CRA notifications, and cannot see your processes, risk assessment or update practices. Article references are to the Regulation as published in the Official Journal; check EUR-Lex for later amendments and implementing acts.