Back to the blog

Cyber Resilience Act from September 2026. You have 24 hours to report a vulnerability – and that does not exempt you from the GDPR

Learn which software products fall under the CRA, when its 24- and 72-hour reporting clocks start, and why GDPR breach notifications remain separate.

Vulnerability confirmed on Friday at 17:40. The technical analysis will not be completed until Monday at the earliest. The 24-hour clock started on Friday – and it will not stop for the weekend. From 11 September 2026, this will no longer be a hypothetical scenario, but an obligation arising from Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA).

If your company develops software sold to businesses or public authorities, the second half of 2026 will bring several independent regulatory changes at once. None of them is addressed explicitly to an “IT company” – each defines a category of entity that you must determine for yourself whether you fall within. This article explains how the two CRA reporting clocks work (24 h and 72 h), why one notification does not replace the other (CRA ≠ GDPR), and what you need to prepare before the first incident occurs.


Key terms before we move on

Before discussing the obligations, it is worth clarifying the terminology. The following terms will appear throughout the article.

Term Meaning
CRA (Cyber Resilience Act) Regulation (EU) 2024/2847 — EU rules on the cyber resilience of products with digital elements. It applies directly, without requiring national implementation.
Product with digital elements Software or computer hardware (and related remote data processing solutions), including components placed on the market separately — Article 3(1) CRA.
Actively exploited vulnerability A vulnerability that the manufacturer knows is already being used by attackers — the 24-hour clock starts from that moment.
CSIRT Computer Security Incident Response Team — the recipient of notifications under the CRA (in Poland: CSIRT NASK, CSIRT GOV or CSIRT MON — the allocation must be confirmed under national legislation).
ENISA European Union Agency for Cybersecurity — a co-recipient of CRA notifications through the single reporting platform.
Articles 33 and 34 GDPR The obligation to notify a personal data breach to the supervisory authority (UODO) within 72 h and to inform individuals where the risk is high.
EPOC (European Production Order) An instrument under Regulation (EU) 2023/1543 — an order addressed directly to a service provider, with a compliance deadline of 10 days (in urgent cases — 8 hours).

Regulation (EU) 2024/2847 — Polish text


What the Cyber Resilience Act changes from September 2026

Two clocks: 24 hours and 72 hours

From 11 September 2026, manufacturers of products with digital elements will be required to report actively exploited vulnerabilities and severe incidents affecting the security of the product. Article 14 CRA introduces a three-stage reporting structure:

Stage Deadline What it includes
Early warning 24 hours after becoming aware The existence of the vulnerability and identification of the Member States in which the product has been made available
Full notification 72 hours after becoming aware General information about the product, the nature of the exploitation, remedial measures taken and measures available to users
Final report 14 days after a corrective measure is made available (actively exploited vulnerability) or 1 month (severe incident) Description of the vulnerability (severity, impact), information about the entities exploiting the vulnerability and details of the updates made available

You submit notifications simultaneously to the CSIRT designated as coordinator and to ENISA — through a single reporting platform (Article 16 CRA). Details of the platform are governed by Delegated Regulation (EU) 2026/881.

The clock starts when you become aware, not when the analysis is complete

This is the most important operational point in the entire article. The 24-hour deadline runs from the moment the manufacturer becomes aware of an actively exploited vulnerability — not from the moment it is confirmed, the technical analysis is completed or management makes a decision.

Returning to the Friday at 17:40 scenario: if your security team received credible information about the vulnerability, the clock is already running. The technical analysis may take three days — but you must submit the early warning by Saturday at 17:40.

You do not need to know the full extent of the problem. Both the CRA and the GDPR allow information to be provided in stages. You must report what you know and supplement it in subsequent steps.

Notification alone does not increase liability

Article 17(4) CRA expressly states that the mere act of notification in accordance with Article 14 or Article 15 does not result in increased liability for the person submitting it. This is important — it removes concerns that a notification amounts to an “admission” of the problem.

Regulation (EU) 2024/2847 — Polish text on EUR-Lex


Which products are subject to the CRA and which are not

The scope of the CRA is determined per product, not per company. Some of your portfolio may be covered, while some may not. This requires an inventory and a reasoned decision for each item.

Product type Subject to the CRA? Comments
Application installed locally on the customer’s premises As a rule, yes A product with digital elements within the meaning of Article 3(1) CRA
Separately licensed component (library, module, SDK) As a rule, yes Placed on the market separately
Pure SaaS (cloud service without a local component) As a rule, no Covered by NIS2, not the CRA
Hybrid model (local component + SaaS backend) Requires analysis The decision depends on what exactly is being made available on the market
Open source made available on a non-commercial basis As a rule, no Monetisation by the manufacturer may trigger the CRA (recital 18)

If your company sells both a desktop application and pure SaaS, the CRA reporting obligations may apply only to the former. However, the procedure must be ready separately for every product covered by the CRA.

Cyber Resilience Act — European Commission


Why the CRA does not replace the GDPR (and vice versa)

This is where companies most often make mistakes. A single event — for example, an actively exploited vulnerability that leads to a personal data leak — may trigger two independent reporting obligations. One notification does not replace the other.

Feature CRA (Article 14) GDPR (Articles 33–34)
What you report An actively exploited vulnerability or a severe product security incident Personal data breach
Who you report it to CSIRT + ENISA (single platform) UODO (President of the Personal Data Protection Office)
Deadline for the initial notification 24 hours after becoming aware 72 hours after becoming aware of the breach (without undue delay)
When you inform individuals Not applicable (the CRA does not provide for such an obligation) Where the breach is likely to result in a high risk to the rights and freedoms of the individual (Article 34 GDPR)
Penalties Requires verification against the Polish-language text of Article 64 CRA and the national implementing legislation Up to EUR 20 million or 4% of annual global turnover

The mechanism works both ways

Information from the manufacturer about a vulnerability triggers the customer’s (data controller’s) assessment of its obligations under Articles 33 and 34 GDPR. If you sell software to businesses, your enterprise customers expect you to notify them of a vulnerability quickly enough for them to assess whether a personal data breach has occurred in their systems.

The Supreme Administrative Court confirmed that the disclosure of a set comprising a person’s first name, surname, address and PESEL number may in itself create a high risk of infringement of the individual’s rights — triggering the obligation under Article 34(1) GDPR to inform the individual without undue delay (Supreme Administrative Court judgment of 1 July 2022 — CBOSA). For the team classifying incidents, this means that a PESEL number combined with identifying data should automatically increase the risk level under the classification rules, without reassessing it from scratch for each event.

Two tracks, one internal procedure

You do not need to build two separate processes from scratch. A safe organisational model is one internal incident assessment form that checks both regimes in parallel — with separate notification submission paths. State explicitly that a CRA notification does not replace a GDPR notification. And vice versa.

Contact us — we will help you design a procedure that combines both tracks without conflating them.


The third clock: 8 hours under the e-evidence rules

Regulation (EU) 2023/1543 on European Production Orders and European Preservation Orders for electronic evidence will apply from 18 August 2026. For providers of SaaS, hosting services and platforms where data storage or processing is an essential component of the service, this creates a new operational obligation.

Parameter Standard procedure Urgent procedure
Deadline for complying with an EPOC 10 days 8 hours
Who issues the order Judicial authority of an EU Member State Judicial authority — marked as urgent
Who complies with it Service provider (or its legal representative in the EU) Service provider

What this means for your company

  1. You must designate a point of contact to receive orders — a person or team available within hours, not days.
  2. You need a process for verifying the authenticity of an order. An EPOC is the form set out in Annex I to the Regulation; verification is based on eIDAS mechanisms (recital 87). You may challenge the authenticity and integrity of the document, the absence of required formal information or a conflict with the law of a third country — but this is not a discretionary refusal. Suspending compliance requires the competent authorities to be informed immediately.
  3. You need a technical mechanism for extracting data precisely within the scope covered by the order — no more and no less.
  4. A service provider without an establishment in an EU Member State must designate a legal representative in writing (Directive (EU) 2023/1544).

Scenario: a SaaS provider receives an order marked as urgent on Friday evening. It has no point of contact or verification process. Eight hours are spent determining who within the company is authorised to make the decision. The risk: disclosing data beyond the scope of the order or missing the deadline.


What else changes in the second half of 2026 — context for software manufacturers

In addition to the CRA and e-evidence rules, a software manufacturer selling to public authorities and businesses should take account of two further regulatory issues.

UODO inspections: entities operating a BIP

UODO’s sectoral inspection plan for 2026 covers, among other things, entities operating a Public Information Bulletin (BIP) — particularly the anonymisation of data and the publication of recordings from meetings of the decision-making bodies of local government units.

Formally, the public authority is the data controller. But if the system you provide does not allow the authority to anonymise part of a recording after publication, set an expiry date for its publication or retain an audit trail of operations performed on recordings — the problem comes back to you as the supplier. The UODO inspection ends with the customer, but the discussion about missing features ends up in your product backlog.

Check three things:

  1. Does your product allow content to be anonymised after publication?
  2. Can an expiry date be set for publication?
  3. Do operations performed on recordings leave an audit trail?

Add any gaps to the next sprint.

AI assessment: per process, not per tool

On 6 August 2026, UODO published four sets of initial question lists concerning the development and use of AI systems — for SMEs, the public sector, entities building their own models and an extended version covering AI Act obligations.

The use of AI must be assessed separately for each process in which AI is used — not once “for the tool”. If your company carried out a single impact assessment for an “AI module” two years ago and considered the matter closed, but the model now supports six different processes (including profiling), the assessment does not cover its actual uses.

For external models (e.g. integration with an external language model), determine the parties’ roles: is the model provider your sub-processor or an independent controller? Check whether the data processing agreements with customers include authorisation for sub-processing.


Checklist: what to prepare before 11 September 2026

You can discuss the following measures at a single meeting of the product and security teams. Each has a specific deliverable.

No. Action Deliverable Priority
1 Take an inventory of your portfolio and identify which products are products with digital elements within the meaning of the CRA — make the decision per product and document the rationale List of products classified as CRA/non-CRA Mandatory
2 Draft a one-page vulnerability reporting procedure covering the 24 h and 72 h clocks, naming the decision-maker and their designated alternate Procedure defining the moment of “becoming aware” Mandatory
3 Combine the CRA procedure with the GDPR breach response process — a single event triggers two parallel assessments, and one notification does not replace the other Integrated incident assessment form Mandatory
4 Verify whether the company falls within the scope of the e-evidence rules; if so, designate a point of contact, an order verification process and a mechanism for extracting data within 8 h Order handling procedure Mandatory
5 Review products for public authorities: anonymisation after publication, publication expiry date and an audit trail of operations performed on recordings List of gaps in the product backlog Mandatory
6 Add PESEL number + identifying data to the incident classification rules as a combination that automatically increases the risk level Updated classification rules Recommended
7 Take an inventory of AI processes and conduct a separate assessment for each process (UODO checklists) Register of AI processes with assessments Recommended
8 For external models, determine the parties’ roles and update data processing agreements to cover sub-processing Updated agreements Recommended
9 Build a rapid incident reporting feature into the product: scope of the breach, list of individuals, access history Product feature Recommended
10 Conduct a dry run: an actively exploited vulnerability on Friday after 17:00 + an urgent data production order with an 8 h deadline Tested procedure Recommended

How the CRA interacts with NIS2, DORA and the AI Act

The CRA does not operate in a vacuum. A software manufacturer may be subject to several reporting regimes at the same time — with different recipients, deadlines and scopes.

Regime Deadline for the initial notification Recipient Entities covered
CRA 24 h (early warning) CSIRT + ENISA Manufacturers of products with digital elements
GDPR 72 h after becoming aware of the breach UODO Personal data controllers
NIS2 Requires verification under national implementing legislation National CSIRT Essential and important entities (including cloud services and platforms)
AI Act 15 days after becoming aware Market surveillance authority Providers of high-risk AI systems

There is no provision establishing a single joint notification for all four regimes. Nor is there any provision that exempts you from the remaining obligations after you report to one authority.

A safe model: one internal incident assessment form that checks all four regimes in parallel — with separate submission paths. The deadline register must account for different starting points (becoming aware, detection, confirmation, determining that a breach has occurred).

Regulation (EU) 2024/2847 — EUR-Lex summary | Regulation (EU) 2024/1689 — AI Act on EUR-Lex


Coordinated vulnerability disclosure — an obligation, not an option

The CRA requires manufacturers to implement a coordinated vulnerability disclosure policy (recital 76) — a structured process under which vulnerabilities are reported to the manufacturer in a way that enables it to diagnose and remedy them before detailed information is publicly disclosed.

This means that the 24/72 h reporting procedure is only one element. In addition, the manufacturer needs:

  1. A channel for receiving reports from external security researchers (e.g. a dedicated email address, form or security.txt file).
  2. Rules for communicating with the reporting person — including a commitment to respond within a specified time.
  3. Optionally: a bug bounty programme as an incentive for responsible reporting.

Manufacturers may use bug bounty programmes, but the CRA does not explicitly require them. It does, however, require a vulnerability reporting channel to exist and be documented.


Preparing for the new reporting obligations — what we can do for you

Preparing for the CRA, the e-evidence rules and changing GDPR requirements is not a project for the legal department in isolation. It is a project that brings together the product, security, legal and operations teams.

We support software manufacturers and SaaS providers through three service options — depending on their stage and scale:

Option What it includes
Operational minimum Classification of products under the CRA and e-evidence rules + a single reporting procedure covering the 24/72 h and 8 h deadlines, aligned with the GDPR breach response process
Solid foundation Procedures + updates to data processing agreements and incident classification rules + review of notification clauses in agreements with enterprise customers
Comprehensive protection All of the above + audit of product features (anonymisation, retention, audit trail) + AI assessment per process + a tabletop exercise with the team

We do not create documents “just in case”. We design procedures where risks actually arise — and test them against scenarios that could occur in your company.

Contact us — together, we will determine which of your company’s products are covered by the new obligations and provide a ready-to-use set of procedures before 11 September 2026.


Three clocks, two tracks, one decision to make now

The CRA introduces reporting obligations that cannot be handled without a designated decision-maker, an alternate and a ready-to-use reporting process. Alongside the CRA’s 24 h and 72 h clocks is the 8 h clock under the e-evidence rules — and the separate 72 h GDPR track. None of these notifications replaces the others.

The scope of the CRA is determined per product. You must have the procedure ready before the first incident — because when the first incident occurs, there will be no time to write it.

If you want to organise your reporting obligations, update your agreements and test your procedures against scenarios relevant to your company — contact us.


Frequently asked questions

Which of my products are subject to the CRA and which are not?
The CRA covers products with digital elements — software or hardware intended to be connected to a device or network, including separately licensed components. Pure SaaS services (without a local component) are generally subject to NIS2, not the CRA. Hybrid models (local component + SaaS backend) require individual analysis. You make the decision per product, not per company — and it is worth documenting the rationale in writing.

When does the 24-hour deadline for the early warning begin?
From the moment the manufacturer becomes aware of the actively exploited vulnerability. Not from confirmation, not from the completion of the technical analysis and not from a management decision. If your security team has received credible information, the clock is running. The CRA allows information to be provided in stages: you report what you know and supplement it in subsequent steps.

Does one notification satisfy both the CRA and the GDPR?
No. These are two separate obligations to different authorities (CSIRT + ENISA vs. UODO), with different deadlines and triggering conditions. A single event may trigger both obligations — but one notification does not replace the other. A safe model is one internal incident assessment form with two separate submission paths.

What do I submit within 24 hours if I do not yet know the scale of the problem?
An early warning — information that an actively exploited vulnerability exists, identifying the Member States in which the product has been made available. You submit a more complete notification (the nature of the exploitation, measures taken and measures available to users) within 72 hours. The final report is due within 14 days after a corrective measure is made available.

As a SaaS provider, can I receive a direct data production order with an 8-hour deadline?
Yes — from 18 August 2026 under Regulation (EU) 2023/1543 on European Production Orders. In urgent cases, the deadline for complying with an EPOC is 8 hours. A service provider without an establishment in an EU Member State must designate a legal representative. The lack of a point of contact and a process for verifying the order’s authenticity is an operational risk that should be eliminated in advance.

What penalties apply for failing to report a vulnerability within the CRA deadline?
The CRA requires Member States to establish rules on penalties (Article 64), but the specific amounts and percentage-of-turnover thresholds must be verified against the Polish-language text of the act and the national implementing legislation. Under the GDPR, penalties for breaching the obligations to report a personal data breach and inform individuals can reach EUR 20 million or 4% of annual global turnover. Liability for breaching the CRA reporting obligations is separate from liability for breaching the essential cybersecurity requirements.

RECOMMENDED

You may also be interested in

Selected examples of projects in which we supported businesses on legal matters, from regulatory and compliance advice to technology projects, transactions and day-to-day business support.