Shipmark / News

The Commission's CRA guidance is in the Official Journal: what app publishers should check

· 6 min read · CRA news

The European Union flag reflected in the glass facade of a modern building in Brussels
Photo: Fabian Kleiser on Unsplash

In short: the European Commission's guidance on applying the Cyber Resilience Act appeared in the Official Journal on 17 November 2026, as a 61-page Communication. The text was approved on 27 July; this is its formal publication.

  • It is non-binding. Only the Court of Justice of the EU can interpret the CRA authoritatively.
  • For app publishers the useful parts are remote data processing (your backend), support periods, what counts as a substantial modification, and reporting.
  • The reporting duty has applied since 11 September 2026, including to apps already on the market.

What happened

The Commission's Guidance on the application of Regulation (EU) 2024/2847 was published in the Official Journal on 17 November 2026. The Commission's own page shows it was first released on 27 July 2026 as document C(2026) 5252. We covered the content of that July release in our piece on PWAs versus native apps. What is new is the formal step: the text is now in the Official Journal, with 67 worked examples according to the Commission and a reference of C/2026/6013 according to InfoEUROPA and Captain Compliance.

The legal basis is Article 26 of the CRA, which tells the Commission to publish guidance for economic operators, with a particular focus on remote data processing solutions, open source and the concept of substantial modification. The guidance says it is not binding, so treat it as the reading that market surveillance authorities are likely to start from, not as law. We read the copy republished by Spain's official gazette.

Your backend can be part of the app

Section 8 matters most here. Under Article 3(2), remote data processing is processing at a distance for which the software is designed and developed by or for the manufacturer, and without which the product could not perform one of its functions. The guidance lists functions such as sending commands, file synchronisation, user onboarding, configuration, automated updates and identity management, and says the processing can run on premises or in a private cloud, not only a public one.

Its mobile banking example is instructive. The bank's own interface server counts as remote data processing, because the app needs it and the bank built it. The core accounting systems do not, since the app does not talk to them directly, although they still create risks to assess. A third-party chat service built into the app is treated as a third-party component, not as part of the product, so you must assess it and exercise due diligence.

If you declare such a solution, the guidance says it belongs in the technical documentation. Our reading: list every server-side service your app needs to work, mark which you built and which you buy, and keep that list with your technical documentation.

Support periods and updates

Article 13(19) requires the end date of the support period to be stated at purchase, at least by month and year. The guidance adds that five years is not a default for every product: where a product is expected to be used longer, the period should be longer. It also repeats the rule in Article 13(10) that a manufacturer of software may fix vulnerabilities only in the latest version, provided earlier users can move to it free of charge. A substantial modification does not automatically restart the support period; the question is whether it changes the factors that set the original one.

For an app this suggests a clear policy: a published end-of-support date, a forced or strongly prompted upgrade path, and no charge for moving to the current version. Our support period guide helps with the dates.

Which releases are substantial modifications

The test is about risk, not the size of the change. You ask whether the update creates new or higher cybersecurity risks that your existing risk assessment did not cover. Security updates are generally not substantial modifications, because their purpose is to reduce risk. Exceptions include an update that changes data flows or adds externally reachable interfaces. Its examples include a messaging app whose later group-chat feature was already covered by the original risk assessment (not substantial), and an app whose new "remember me" login adds risks (substantial). Run the release check against your next major version.

Reporting is already live

QuestionWhat the guidance and the CRA say
Does it cover apps already in the stores?Yes. Article 14 has applied since 11 September 2026 to all in-scope products, including those placed on the market earlier.
Exploitation known before 11 September?Not reportable retroactively. If you learn of exploitation after that date, the duty applies.
Deadlines (Article 14(2))Early warning within 24 hours, notification within 72 hours, final report within 14 days after a fix or mitigation is available.
Flaw in a third-party SDK?Reportable if it is actively exploited in your product. If it cannot be exploited there, reporting is voluntary, but you still handle it and tell the upstream maintainer.

The clock starts when you have a reasonable degree of certainty after a prompt initial assessment. Our reporting guide and deadline calculator turn this into dates.

What we would do this week

  1. Download the guidance and read section 8 and the support-period section with your engineering lead.
  2. Write down every backend service your app depends on, and mark each as your own or third-party.
  3. Decide the support end date for each app and where you will state it for users.
  4. Check that your incident runbook can produce a 24-hour warning, including for third-party SDKs.
  5. If an agency builds your app, make sure the contract says who keeps the backend and release documentation up to date. You, as the publisher, remain the manufacturer.

Backend, SDKs and release notes all start from knowing what is in each build. Generate an SBOM and check it against known vulnerabilities in seconds.

Open the free scanner

Sources

This article summarises non-binding Commission guidance and EU law for practical use. Details come from the Spanish-language text and secondary summaries, so check the passages that matter to you in the Official Journal. It is not legal advice. Related: Does the CRA apply to mobile apps? · CRA and companion apps