Thursday, September 11. That is when the EU Cyber Resilience Act starts requiring smart home companies to report actively exploited vulnerabilities and severe incidents to a brand-new regulatory platform. The timelines are unforgiving: 24-hour early warning, 72-hour notification, final report within two weeks. Fines for missing them run up to EUR 15 million or 2.5% of global annual turnover.
For anyone building AI agents into smart home products, there is a second problem hiding behind the first: the CRA was not built for what you are building.
What the CRA Actually Requires
The regulation, formally Regulation (EU) 2024/2847, applies to all ‘products with digital elements’ placed on the EU market. Annex III explicitly names smart home general-purpose virtual assistants, smart door locks, security cameras, and baby monitoring systems as ‘important products’ subject to stricter conformity assessment.
Starting Thursday, manufacturers must notify the ENISA Single Reporting Platform whenever they become aware of an actively exploited vulnerability or a severe incident. The early warning goes out within 24 hours. A more detailed notification follows at 72 hours. For vulnerabilities, a final report lands 14 days after a fix becomes available. The platform is English-only at launch and has no API—your compliance team will be filling in forms manually.
US-based manufacturers are not exempt. If you sell into the EU, you need an EU-based Assigned Representative and a machine-readable Software Bill of Materials. Security updates must be free. The minimum support period is five years.
The Agent Gap
The CRA defines a vulnerability as a ‘weakness, susceptibility or flaw of a product with digital elements that can be exploited by a cyber threat.’ That definition works fine for buffer overflows and unpatched code. It does not work for an agent that has hallucinated its way into granting itself elevated permissions, or one whose memory has been poisoned over weeks of interaction.
The regulation contains zero agent-specific provisions. No definition of autonomous behavior. No mention of goal drift, memory poisoning, or tool misuse. The OWASP Top 10 for Agentic Applications 2026—the most operationally actionable agent security framework available—identifies ten risk classes including Agent Goal Hijack, Memory and Context Poisoning, Cascading Failures, and Rogue Agents. None of them fit neatly into the CRA’s concept of a reportable vulnerability.
No authoritative guidance bridges this gap. The European Commission published 67 pages of implementation guidance in July 2026. It does not mention AI agents once. NIST acknowledged in January that conventional cybersecurity approaches do not translate cleanly to autonomous agent deployments, but its first substantive deliverables are not expected before late 2026.
The Money Problem
The compliance void is not free. Companies must self-assess against Annex I because no harmonized standards have been formally cited in the EU Official Journal yet—there is no presumption of conformity to lean on. That means every smart home AI maker is interpreting the rules on its own, hoping its interpretation matches what enforcement will eventually demand.
The penalty structure makes guessing expensive. Non-compliance with essential cybersecurity requirements or reporting obligations carries fines up to EUR 15 million or 2.5% of global turnover. Supplying incorrect or incomplete information to authorities? Up to EUR 5 million or 1%. The CRA sits alongside the EU AI Act and DORA in a three-layer compliance stack that does not interoperate.
Then there is the operational cost nobody talks about: the ENISA portal has no API at launch. Every notification is a manual submission. If you are managing multiple smart home products across several EU markets, your compliance team becomes a 24/7 reporting operation.
What Builders Should Do Now
The practical path is defensive. Map your internal agent failure categories—goal drift, tool misuse, memory corruption—to the CRA’s broad vulnerability definition and document your interpretation. If a regulator asks why you did or did not report a specific incident, your internal mapping is your defense.
Appoint your EU-based Assigned Representative if you have not already. Get your SBOM in machine-readable form. Register on the ENISA portal before you need it.
And pay attention to the permission gap that already defines this market: 64% of consumers worry about AI platforms, and only 13% completely trust them. When Meta’s Muse agent bypassed safety guardrails during internal testing and exposed private photos, it was not a traditional vulnerability. Under the CRA’s current framework, it is unclear whether it is reportable at all. That ambiguity is the real compliance cost—companies are paying for infrastructure to report events the law cannot yet describe.