Shipmark / News

ENISA upgraded the CRA reporting platform to version 1.3: what app teams should check

· 5 min read · CRA news

A round grey alarm clock on a desk, shown out of focus
Photo: Stanisław Gregor on Unsplash

In short: on 4 November 2026 ENISA upgraded the CRA Single Reporting Platform (SRP) to version 1.3 without publishing release notes, after adding two FAQ answers on 15 October that matter if you ever file a report.

  • ENISA's hub page says the platform went to version 1.3 on 4 November 2026 and that its documentation is still being updated.
  • The FAQ now says only the coordinating CSIRT can close a report, and that ENISA may ask to add a fixed vulnerability to the EU vulnerability database, with your agreement.
  • Nothing here changes the law: the 24-hour, 72-hour and final-report deadlines of Article 14 are the same, and have applied since 11 September 2026.
  • For an app team, the lesson is practical: your internal reporting runbook can go stale in weeks, so check it against the live platform.

What changed, and what did not

Reporting of actively exploited vulnerabilities and severe incidents under the Cyber Resilience Act has been live since 11 September 2026, through a platform run by ENISA. Two months in, the platform and its documentation are still moving. The ENISA hub page states: "On 4 November 2026, the CRA SRP was upgraded to version 1.3." It adds that the documentation on the site is being updated to reflect the changes, and tells readers to check release dates for the current version.

The independent site cyberresilienceact.eu, in a status note of 15 November, reports an earlier upgrade to 1.2.1 on 20 October that changed how a primary representative invites secondary representatives or backups. We could only find that detail in that note, not on ENISA's pages, so treat it as a secondary report. The same note observes that ENISA published no release notes for either upgrade, and in our reading of the hub page that is still the case: the four guidance pages it lists carry September 2026 dates.

The reissued Assigned Representative user manual, version 1.3 (November 2026), is the clearest picture of the platform today. It says an invitation to a secondary representative expires after seven days and can be revoked, that a primary representative needs a verified association with the manufacturer before inviting anyone, and that an unverified representative can make up to 20 submissions while validation is pending. It also says drafts are private to the person who created them, so a colleague on the same manufacturer account cannot pick up your draft. Voluntary reporting under Article 15 is not available in the initial release, and the FAQ says there is no API at launch.

Two FAQ answers worth knowing before an incident

ENISA's FAQ was last updated on 15 October 2026 and now has 35 entries. Two additions stand out, and an Edge SDN summary of the update agrees with the ENISA text.

FAQWhat it saysWhy an app team cares
34 (new)Only the CSIRT designated as coordinator can close or invalidate a report. You can ask it to, including through an "additional note".A mistaken or duplicate submission is not yours to withdraw. Decide who files, and check the details before you submit.
35 (new)Under Article 17(5), ENISA may add a publicly known, notified vulnerability to the EU vulnerability database once a fix or mitigation exists, with the manufacturer's agreement. ENISA may contact you, and as a CVE numbering authority can help assign a CVE ID.Someone must be ready to answer ENISA, and the answer should match what you tell users in your own advisory.
24 (updated)The platform is English only for now; other languages are "under review".Your on-call person must be able to file in English under time pressure.

The FAQ also explains two things that surprise people. The 72-hour counter currently runs from 48 hours after the early warning, so it can show a report as overdue early; a later release is meant to use the time you became aware. And there is no retrospective duty: if you were already aware of an exploited vulnerability before 11 September 2026, the FAQ says you do not have to report it, but awareness after that date triggers the duty.

The deadlines themselves

These come from the law, not the platform. We checked them against Regulation (EU) 2024/2847 on EUR-Lex. Under Article 14(2), for an actively exploited vulnerability you send an early warning without undue delay and within 24 hours of becoming aware, a notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available. Article 14(4) uses the same 24 and 72 hours for severe incidents, with the final report due within one month of the notification. Article 16(1) is the basis for the single platform.

A live example arrived on 21 October 2026, when the Commission, ENISA, CERT-EU, Europol's EC3 and the EU CSIRTs network issued a joint statement on two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, both allowing unauthenticated remote code execution. The statement reminded manufacturers that, since 11 September, they must report actively exploited vulnerabilities through the platform, and told organisations to check third-party products because many use PHP in the background. If your app's backend or a bundled web view component uses PHP, that is the kind of dependency chain an SBOM should show you.

What it means for app teams

The legal text is stable, but the tool you will use under pressure is not. Version changes that arrive without release notes, and guidance pages dated before them, mean a runbook written in September may no longer match the screens. That is our reading, not an ENISA statement. The risk is not that the platform is bad; it is that the first time your team meets a change is during a 24-hour clock.

What we would do this week

  1. Open the v1.3 user manual and compare it with your internal runbook, in particular the steps for registering a representative and inviting a backup.
  2. Check that your primary and at least one secondary representative are registered, verified and able to log in with EU Login and a second factor. Invitations expire after seven days, so do not leave this for an incident.
  3. Add two lines to the runbook: filing mistakes are corrected through the coordinating CSIRT, and one named person answers if ENISA asks about the vulnerability database.
  4. Remember that drafts are per person, so agree who writes the early warning and who can take over.
  5. Rehearse once, with a fake incident and a stopwatch, and use our reporting deadlines tool to see your 24-hour, 72-hour and final dates.

Knowing which vulnerable component is in which app version is the first minute of any report. Build an SBOM and check it against known vulnerabilities in seconds.

Open the free scanner

Sources

This article summarises ENISA documents and EU law for practical use. The platform may change again after publication. It is not legal advice. Earlier coverage: EU agencies' fridge-hack statement and CRA reporting · CRA vulnerability reporting for app teams