Summary
- Article 14's authority-facing chain prints four intervals — 24 hours, 72 hours, 14 days and one month — and every one of them is anchored to an act of the manufacturer rather than to an event outside the firm.
- The one duty addressed to the product's users, Article 14(8), carries no hour, day or month; the only temporal expression in the paragraph sits inside a coordinating CSIRT's fallback power.
Take a manufacturer that learns at nine in the morning that someone is exploiting a flaw in a product it has already sold. Regulation (EU) 2024/2847, the Cyber Resilience Act, starts three clocks that day. An early warning is due "without undue delay and in any event within 24 hours of the manufacturer becoming aware of it". A vulnerability notification is due within 72 hours of the same moment. A final report is due "no later than 14 days after a corrective or mitigating measure is available". Those are the intervals in Article 14 as reproduced in full text.
Look at what each clock is nailed to. The first two run from an event inside the company's head — the moment it becomes aware. The third runs from an event inside the company's own schedule: the moment a corrective or mitigating measure exists, which is a date the manufacturer itself declares. Nothing in this chain starts from a regulator's request, a customer's complaint or a researcher's public disclosure. Four intervals, and not one anchor belongs to a party outside the firm.
That is the first finding and it is structural rather than moral. A deadline anchored to the regulated party's own act is a deadline the regulated party can, within limits, time.
Article 14 in fact carries two parallel chains. Actively exploited vulnerabilities sit in paragraphs 1 and 2 on the 24-hour, 72-hour and 14-day pattern above. Severe incidents sit in paragraphs 3 and 4, and their final report falls due one month after the manufacturer's own 72-hour notification; the Commission's reporting-obligations page and ENISA's Single Reporting Platform FAQ both describe it that way. Paragraphs 3 to 6 were not read verbatim for this piece, so the two-chain description rests on those two official texts rather than on article text I hold — and one month is left as a month, because nothing read here converts it into a day count.
Both chains point one way. The notification goes "simultaneously to the CSIRT designated as coordinator … and to ENISA", through the single reporting platform established under Article 16. Article 16 itself was not read here, so nothing below characterises how that platform is built. ENISA — the European Union Agency for Cybersecurity, recorded in the BTW directory — is named in the Article itself as a recipient, alongside a national coordinator. Where the manufacturer's Union main establishment sits determines which coordinator receives the filing, and where there is no main establishment Article 14(7) fixes the recipient by cascade: authorised representative, then importer, then distributor, then the Member State with the most users.
One divergence deserves printing. The Commission's page says the information is made available to ENISA simultaneously "unless particularly exceptional circumstances apply". That qualifier appears in the Commission's gloss and not in the Article text held here. Both surfaces can be accurate about different things, but a reader who compares them is reading two instruments, and only one of those instruments carries the qualifier.
Then there is paragraph 8, the only place in Article 14 where the person holding the product appears. After becoming aware of an actively exploited vulnerability or a severe incident, "the manufacturer shall inform the impacted users of the product with digital elements, and where appropriate all users, of that vulnerability or incident", and where necessary of the mitigation and corrective measures those users can deploy, where appropriate in a structured, machine-readable format. A second unofficial reproduction carries identical wording for the paragraph.
Count the units in that sentence. There are none. No hour, no day, no month.
The only temporal expression in the paragraph sits in its second sentence, and it belongs to somebody else: where the manufacturer fails to inform users "in a timely manner", notified CSIRTs designated as coordinators may provide that information to users when proportionate and necessary. "In a timely manner" is not a deadline and cannot be stretched into one. It is the trigger for a discretion held by a regulator, not a bound on the firm. Whether any coordinating CSIRT has used that discretion is not something the material read here establishes.
The asymmetry has a practical edge. A buyer of a product with an actively exploited vulnerability is the party who can act — patch it, isolate it, stop using it — and is also the party with no printed interval governing when they learn. A duty to tell the regulator is not a duty to tell the buyer, and this regulation does both, in the same Article, with a unit attached to only one of them.
The counterweight is real and belongs in the piece. This is the first instrument on this desk that makes a manufacturer owe its users a sentence at all. And paragraph 8 is not the only public surface: Annex I, Part II requires manufacturers to share and publicly disclose information about fixed vulnerabilities once a security update is available — description, affected product, impacts, severity, remediation — with a justified delay permitted where the risks of publication outweigh the benefits. Part II(8) requires security updates to be disseminated without delay, free of charge unless otherwise agreed with a business user for a tailor-made product, accompanied by advisory messages including on potential action to be taken.
So the regulation does create a public record of the fix. What the material read here does not show is any requirement to publish the notification itself, or any per-notification identifier a stranger could use to check one case. Those are two different artefacts: the fixed hole, and the fact that the company was told about it.
One more limb sits off to the side. Article 24 puts a documentation duty on open-source software stewards — a cybersecurity policy, kept in a verifiable manner, covering secure development and effective vulnerability handling — and Article 24(3) extends Article 14(1) to a steward only "to the extent that they are involved in the development of the products with digital elements", with 14(3) and 14(8) extended only where severe incidents affect the network and information systems the steward provides for that development. A great deal of work is being done by one conditional clause.
The calendar is straightforward. The Commission records the Act in force on 10 December 2024, reporting obligations applying from 11 September 2026, and the main obligations from 11 December 2027, with steward reporting under Article 24(3) on that later date (Commission policy page). The reporting duty is therefore live now, while most of the product rules are not.
An arithmetic note of my own, not the regulation's: if a corrective or mitigating measure happens to be available on the day the manufacturer becomes aware, the three vulnerability intervals collapse into 24 hours, 72 hours and 17 days from that day. No document prints 17. I do, and only as arithmetic, because the 14-day report runs from the fix rather than from awareness.
On sourcing: the Official Journal landing page for Regulation (EU) 2024/2847 was read at its header, its publication metadata and its opening recitals. The operative wording above comes from two self-declared unofficial reproductions, one of which omits paragraphs 5 and 6 without supplying their text; only the Official Journal text is authentic, and a reproduction is not it. The two Commission pages are official summaries and the ENISA FAQ is agency operational guidance, not legal text.
What this adds to what BTW has already published: a literal search for "Cyber Resilience Act" on 19 November 2026 returned one row — a December 2024 profile of the compliance timeline for open-source projects — and a search for "ENISA" returned a September 2026 briefing on the reporting platform opening without an automated submission interface, plus a November 2026 research row on the NIS2 proposal widening the ENISA register while the access clause still names the older, narrower list.
None of the three reads Article 14's addressee structure, the anchor set of its intervals, the absence of a unit on the user-facing limb, or the relation between the notification and the Annex I public-disclosure duty. That is the delta claimed here.
And the edges, stated inside the same sentence as the finding: across the eight documents read for this piece on 19 November 2026 — the Official Journal landing page, two reproductions of Article 14, one of Article 24, one of Annex I, two Commission pages and one ENISA page — no provision requiring publication of an individual Article 14 notification, and no per-notification public identifier, was located. Article 16 was not read. Paragraphs 5 and 6 of the Article 14 reproduction were not read. The delegated act adopted on 11 December 2025 on grounds for delayed dissemination among CSIRTs was not read, and nothing here characterises it.
Which leaves the shape of the thing. The CRA hands the regulator a clock with four intervals on it and hands the buyer a verb. The verb is not nothing; it is more than any instrument on this desk offered before. But a firm that must speak within 24 hours to an agency and at no printed hour to its own customers has been told exactly who was expected to move first. The buyer finds out from a patch note, a press cycle or an attacker, on a schedule this instrument does not set.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






