← CRA Glossary
CVD & Vulnerability Management

Remediation Timeline

A remediation timeline defines the expected period between a vulnerability being identified (or reported) and a fix being developed, tested, and released to users. The CRA requires manufacturers to address vulnerabilities 'without undue delay' - remediation timelines operationalise what this means for different severity levels.

A remediation timeline defines the expected period between a vulnerability being identified (or reported) and a fix being developed, tested, and released to users. The CRA requires manufacturers to address vulnerabilities 'without undue delay' - remediation timelines operationalise what this means for different severity levels.

CVD & Vulnerability Management

Last updated 19 July 2026

What Is a Remediation Timeline?

A remediation timeline is the defined period within which a manufacturer commits to delivering a fix for an identified vulnerability - from initial identification or validated report receipt to a security update being available to users. Remediation timelines are a component of a manufacturer's broader vulnerability handling policy and PSIRT processes. They set internal SLAs for engineering teams and provide predictability for security researchers and users who need to plan their own risk mitigation. The CRA's requirement to address vulnerabilities 'without undue delay' is intentionally vague - it does not set specific days - but regulators and standards bodies treat severity-differentiated SLA frameworks as the accepted method for demonstrating what 'without undue delay' means in practice.

CRA reference:Article 13, Annex I

Setting Severity-Based SLAs

Industry best practice and ISO/IEC 30111 (vulnerability handling processes) both recommend severity-differentiated remediation timelines. A typical framework:

  • Critical (CVSS 9.0–10.0): Patch within 30 days; interim mitigation guidance within 5 days.
  • High (CVSS 7.0–8.9): Patch within 60 days; interim guidance if exploitation is plausible.
  • Medium (CVSS 4.0–6.9): Patch within 90 days, included in the next scheduled release cycle.
  • Low (CVSS 0.1–3.9): Patch within 180 days or included in the next major version.
  • Actively exploited (any CVSS): Treat as Critical regardless of base score; notify ENISA within 24 hours per CRA Article 14.

These SLAs should be documented in the manufacturer's PSIRT policy and published as part of the CVD policy where appropriate.

CRA reference:Article 13, Article 14, Annex I

Factors That Affect Remediation Time

Several factors legitimately extend or compress remediation timelines:

  • Root cause complexity: A vulnerability requiring architectural changes to the product's authentication model takes longer than a missing bounds check.
  • Testing requirements: Safety-critical products (medical devices, industrial controllers) require extensive regression testing before any patch release.
  • Update mechanism limitations: Products without over-the-air update capability may require field service interventions, dramatically extending the time between patch availability and user protection.
  • Dependency on upstream vendors: When the vulnerability is in a third-party library, the manufacturer must wait for an upstream patch before they can integrate and release their own fix.
  • Multi-vendor coordination: Simultaneous disclosure with other affected manufacturers requires all parties to be ready before release.

Manufacturers should document these factors in their triage records to justify timelines that extend beyond SLA targets.

CRA reference:Article 13

Measuring and Improving Remediation Performance

Tracking remediation performance against defined SLAs enables continuous improvement and provides audit evidence for CRA compliance. Key metrics include: mean time to remediate (MTTR) by severity band; percentage of vulnerabilities remediated within SLA; percentage of vulnerabilities with interim mitigation guidance issued; and SLA miss rate with documented justifications. These metrics should be reviewed in regular PSIRT process reviews and reported to senior management as part of the product security function's accountability framework. Manufacturers with consistently high SLA miss rates for critical vulnerabilities are at elevated CRA enforcement risk and should treat this as a signal to invest in remediation capacity or process improvement.

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

What does 'without undue delay' mean in practice under the CRA?+

'Without undue delay' is the CRA's standard for vulnerability remediation speed. It is intentionally flexible to accommodate different product types and vulnerability complexities. In practice, regulators and standards bodies treat it as requiring severity-proportionate timelines - critical vulnerabilities should be addressed within weeks, not months; low-severity issues may be addressed in routine release cycles. Manufacturers that can demonstrate documented SLAs with strong compliance rates are in a much stronger position than those without any defined timelines.

Is there a minimum required remediation time for critical vulnerabilities under EU law?+

The CRA does not specify a mandatory number of days for critical vulnerability remediation. ENISA's guidance and ISO/IEC 30111 suggest 30 days for critical vulnerabilities as a best practice baseline. For actively exploited vulnerabilities, the urgency is highest and manufacturers should prioritise immediate interim mitigations (configuration guidance, feature disablement instructions) even before a full patch is available, to reduce exposure during the remediation period.

What should manufacturers do when a patch is ready but the update mechanism cannot deliver it rapidly?+

When a patch exists but cannot be delivered quickly - for example, because the product requires manual update procedures or is deployed in air-gapped environments - manufacturers should immediately publish a security advisory with: the vulnerability details; the available patch version; step-by-step update instructions; and interim mitigation measures users can apply to reduce risk while updating. This advisory publication satisfies the CRA's user notification obligation even when patch deployment takes longer than the remediation SLA.

Sector checklists covering Remediation Timeline

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)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.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 Remediation Timeline fits into your complete CRA compliance programme.

View checklists →