All templates
Free Template

What should a supplier contract require under CRA Article 13(5) and 13(6)?

A supplier contract under CRA Article 13(5) and 13(6) should require an SBOM with each component version, security updates for at least the product's support period, vulnerability notice within set hours, a channel for upstream reports, agreed fix costs and ownership, testing and audit rights, and records kept for 10 years.

Last updated 14 November 2026

ForManufacturers selling into the EU that integrate third-party software, firmware or hardware components, and the procurement and legal teams who negotiate those supply agreements
CRA Articles
Article 13(5)Article 13(6)Article 13(8)Recital 34Annex I Part II

User Manual: How to Use This Functionality

Implementation Guide

1. Purpose and Scope

This template provides the legal and technical structure for What should a supplier contract require under CRA Article 13(5) and 13(6)?. It addresses obligations under Article 13(5) and Article 13(6) and Article 13(8) and Recital 34 and Annex I Part II for Manufacturers selling into the EU that integrate third-party software, firmware or hardware components, and the procurement and legal teams who negotiate those supply agreements.

2. Customisation Instructions

  • Replace all bracketed placeholders [LIKE THIS] with your specific details.
  • Review section guidance notes to align terms with your product operations.
  • Agree each time limit and amount with the supplier before signing.

3. Deployment and Maintenance

Attach the signed schedule to the supply agreement. Keep the signed copy with the technical documentation of each product that integrates the component. Review the schedule at each renewal.

4. Platform Automation

CVD Portal records the due diligence for each component of a product, including CE marking status, maintenance status and supplier support gaps, and sends upstream vulnerability reports to the component maintainer.

Access Template · Magic Link Required

Unlock What should a supplier contract require under CRA Article 13(5) and 13(6)?

Enter your work email to receive a single-use magic access link. Clicking the link in your email verifies your domain and unlocks all templates.

Key takeaways

  1. Article 13(5) requires manufacturers to exercise due diligence when they integrate components sourced from third parties.
  2. Recital 34 lists the checks: CE marking, security update history, vulnerability databases and additional security tests, scaled to the risk.
  3. Article 13(6) requires manufacturers to report a vulnerability in an integrated component to its maintainer and to share any fix they develop.
  4. A supplier contract cannot move CRA responsibility, but it can secure the SBOMs, notices and fixes that the manufacturer needs.
  5. A supplier refusal must be documented and reflected in the risk assessment of the product.

When to Use This Schedule

Article 13(5), Article 13(6), Article 13(8), Article 71(2)

Attach this schedule to the supply agreement for each component that [MANUFACTURER NAME] integrates into a product with digital elements. A component is any software library, firmware, module or hardware part that the supplier makes and maintains.

  • Article 13(5) and 13(6) apply from 11 December 2027 under Article 71(2).
  • Article 14 reporting applies from 11 September 2026. A supplier notice is often the first sign of an actively exploited vulnerability, so put the notice clauses in place now.
  • The support period is at least five years in most cases (Article 13(8)). A contract signed today runs into the period that the CRA covers.

This schedule is for commercial suppliers. An open-source project with no contract is reached through its own security policy, as Section 7 explains.

Note

Sign the schedule as part of each new or renewed supply agreement. For suppliers already under contract, send it as an amendment with the next order or renewal.

Parties and Definitions

Article 3

Manufacturer: [MANUFACTURER LEGAL NAME], [ADDRESS], [REGISTRATION NUMBER]. Supplier: [SUPPLIER LEGAL NAME], [ADDRESS], [REGISTRATION NUMBER]. Component: [COMPONENT NAME, PART NUMBER OR PACKAGE NAME], versions [VERSION RANGE], as listed in Annex A of this schedule. Product: the product with digital elements of the Manufacturer into which the Component is integrated, namely [PRODUCT NAME AND MODEL]. Vulnerability: a weakness, susceptibility or flaw of the Component that can be exploited by a cyber threat. Actively Exploited Vulnerability: a Vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the permission of the system owner. Support Period: the period set in Section 5.

Note

Keep the definitions close to the CRA wording in Article 3, so the parties do not argue later about whether an event triggers a clause.

Component Information and SBOM

The Supplier shall deliver, with each version of the Component:

  1. A software bill of materials (SBOM) in [CycloneDX / SPDX] format that covers at least the top-level dependencies of the Component.
  2. The version identifier and a cryptographic hash of each delivered file.
  3. A list of known vulnerabilities in the Component at the date of delivery, with their status.

The Supplier shall deliver an updated SBOM within [10] working days of any new version, and at any time on request within [5] working days.

Note

Annex I Part II point (1) requires the Manufacturer to identify and document the components of the Product, with an SBOM that covers at least the top-level dependencies. Without the supplier SBOM, the Manufacturer cannot meet this duty for the inside of a binary component.

Conformity Status of the Component

Recital 34, Article 28

Where the Component is itself a product with digital elements placed on the EU market, the Supplier shall:

  1. Confirm in writing that the Component bears the CE marking under Regulation (EU) 2024/2847, or state the date by which it will.
  2. Provide the EU declaration of conformity for the Component on request.
  3. Inform the Manufacturer within [10] working days if the conformity of the Component is withdrawn or challenged by an authority.

Where the Component is not placed on the market on its own, the Supplier shall provide the information in Sections 3, 5 and 6 instead.

Note

Recital 34 names a check on CE marking as one way to do due diligence. A CE mark on a component does not move responsibility for the Product. The Manufacturer stays responsible for the conformity of the whole Product.

Support Period and Security Updates

Article 13(8), Article 13(9),

The Supplier shall provide security updates for the Component until [DATE], or for [NUMBER] years after the last delivery, whichever is later (the Support Period).

During the Support Period the Supplier shall:

  1. Fix each Vulnerability in the Component without undue delay, and within [30] days for a Vulnerability rated critical or high.
  2. Deliver security updates separately from functionality updates where this is technically possible.
  3. Keep each security update available to the Manufacturer for [10] years after its release.
  4. Give the Manufacturer at least [12] months notice before the end of the Support Period.
Note

Article 13(8) lets the Manufacturer take into account the support periods of integrated components that provide core functions. Set the Supplier's support period at least as long as the Product's own support period. A shorter one leaves the Manufacturer to fix the Component alone.

Vulnerability Notification by the Supplier

Article 14(1), Article 14(2), Article 13(7)

The Supplier shall notify the Manufacturer at [SECURITY CONTACT EMAIL]:

  1. Within [24] hours after the Supplier becomes aware of an Actively Exploited Vulnerability in the Component, or of a severe incident that affects the security of the Component.
  2. Within [5] working days after the Supplier confirms any other Vulnerability rated critical or high.
  3. Before public disclosure of any Vulnerability in the Component, with the planned disclosure date.

Each notice shall include the affected versions, a description, any known exploitation, available mitigations and the expected date of a fix. The Supplier shall update the notice when new facts become available.

Note

Under Article 14 the Manufacturer has 24 hours from its own awareness to send an early warning. The 24-hour supplier notice gives the Manufacturer a chance to meet that clock. Article 13(7) also requires the Manufacturer to document relevant information from third parties, so keep every supplier notice.

Upstream Reports from the Manufacturer

Article 13(6); Commission guidance C(2026) 5252 points 222 to 229

Where the Manufacturer identifies a Vulnerability in the Component, it shall report it to the Supplier through [SUPPLIER SECURITY CONTACT OR CVD POLICY URL].

The Supplier shall:

  1. Acknowledge the report within [3] working days.
  2. Give an assessment and a planned fix date within [10] working days.
  3. Keep the report confidential until a fix is available or until the agreed disclosure date.

Where the Manufacturer has developed a code change or documentation to address the Vulnerability, it shall share it with the Supplier, where appropriate in a machine-readable format. The Supplier is not obliged to adopt that change.

Note

Article 13(6) requires the Manufacturer to report a Vulnerability in an integrated component to whoever makes or maintains it, and to share its fix. Commission guidance C(2026) 5252 adds that the report covers the integrated version, should use the maintainer's own channel, and is not owed when the maintainer already knows. For an open-source component with no contract, report through the project's security policy instead.

Fixes, Costs and Intellectual Property

Article 13(6)
  1. The Supplier bears the cost of fixing Vulnerabilities in the Component during the Support Period.
  2. Where the Manufacturer shares a code change under Section 7, [the Manufacturer keeps ownership and grants the Supplier a non-exclusive, royalty-free licence to use it / the Supplier may use it under the licence of the Component].
  3. Where the Supplier does not deliver a fix by the agreed date, the Manufacturer may apply its own mitigation to the Component as integrated in the Product, and [the Supplier shall reimburse reasonable costs up to [AMOUNT] / each party bears its own costs].
Note

Agree on cost and ownership before a Vulnerability exists. During an incident there is no time to negotiate a licence for a patch.

Security Testing and Audit

Recital 34,
  1. The Supplier shall test the security of each release of the Component, and give the Manufacturer a summary of the results on request.
  2. The Manufacturer may, at its own cost and with [20] working days notice, have an independent tester test the Component as integrated in the Product.
  3. The Supplier shall answer a written security questionnaire from the Manufacturer once per year, and after any severe incident.
  4. The Manufacturer may share test results and Supplier answers with a notified body or a market surveillance authority, under confidentiality.
Note

Recital 34 lists additional security tests as one form of due diligence, scaled to the risk of the component.

Changes to the Component

Article 2(6)

The Supplier shall give the Manufacturer at least [90] days written notice before it:

  1. Changes the hardware, the firmware architecture or a security function of the Component.
  2. Moves production to another site or to a subcontractor.
  3. Replaces a third-party dependency that provides a core function.

A replacement part counts as identical only if it is made to the same specifications as the part it replaces.

Note

Article 2(6) excludes spare parts only when they replace identical components and are made to the same specifications. A changed part can need a new assessment of the Product.

Records and Cooperation with Authorities

Article 13(13)
  1. The Supplier shall keep the information it provides under this schedule for [10] years after the last delivery of the Component.
  2. The Supplier shall provide, within [10] working days of a request, the information that the Manufacturer needs to answer a market surveillance authority about the Component.
  3. Where an authority requires corrective action on the Product because of the Component, the Supplier shall cooperate in that action.
Note

Article 13(13) requires the Manufacturer to keep its technical documentation for at least 10 years after placing the Product on the market, or for the support period if longer. The Supplier's records feed that file.

If the Supplier Refuses or Stops Support

Article 13(7), Article 13(2)

Where the Supplier refuses a clause of this schedule, or ends support for the Component, the Manufacturer shall:

  1. Record the refusal and its date.
  2. Update the cybersecurity risk assessment of the Product to reflect the gap.
  3. Choose a response: compensating controls in the Product, its own maintenance of the Component, or replacement of the Component by [DATE].
  4. Record the decision and the reason in the technical documentation.
Note

A refusal does not reduce the Manufacturer's duties. Article 13(7) requires the Manufacturer to document relevant information from third parties and to update the risk assessment where applicable. A documented decision is the evidence that due diligence took place.

Liability and Remedies

Article 64

[LIABILITY CAP, INDEMNITY FOR REGULATORY FINES OR RECALL COSTS, TERMINATION RIGHTS, GOVERNING LAW AND JURISDICTION]

This section depends on national contract law and on the commercial terms of the supply agreement. Agree it with legal counsel.

Note

Article 64 sets fines for the Manufacturer, not the Supplier. Whether a supplier must bear part of that cost is a contract question. This template is not legal advice.

Record supplier due diligence per product

The trial records the due diligence for each component, keeps supplier evidence in the technical file and sends upstream reports to component maintainers.

Start my 14-day compliance trialStart your 14-day compliance trial

Frequently asked questions

Ready to go beyond the template?
The trial keeps each supplier's evidence with the products that integrate the component.
Start my 14-day compliance trialStart your 14-day compliance trial

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