cd /news/ai-policy/the-ai-did-it-won-t-save-you-when-eu… · home topics ai-policy article
[ARTICLE · art-18395] src=dev.to pub= topic=ai-policy verified=true sentiment=↓ negative

"The AI did it" won't save you when EU regulators come knocking

The EU Cyber Resilience Act's vulnerability reporting requirements take effect in September 2026, with full compliance mandatory by December 2027, applying to any product with digital elements sold in the EU market. Engineering teams that have accelerated shipping velocity using AI coding assistants like Copilot, Claude, or Cursor face a structural feature of the regulation: AI-generated code carries the same legal weight as hand-written code, and "the AI did it" is not a valid defense. Security researchers have demonstrated that AI-generated code reintroduces known CVE patterns at meaningful rates, meaning teams shipping such code without a review layer are building compliance debt that will come due when EU regulators enforce the CRA.

read2 min publishedMay 30, 2026

The EU Cyber Resilience Act has been on everyone's "we'll deal with it later" list since it entered into force in December 2024. Later is arriving: vulnerability reporting requirements kick in September 2026, and full compliance is mandatory by December 2027.

The timing matters because of what's happening in parallel: most engineering teams have accelerated shipping velocity by leaning hard on AI coding assistants. Copilot, Claude, Cursor — pick one. The code ships faster. The bugs ship faster too. And under the CRA, you own every line of it.

"The AI did it" won't save you when EU regulators come knocking.

That's not just a headline. It's a structural feature of the regulation.

The CRA applies to any product with digital elements placed on the EU market — hardware, software, apps, APIs. If you have EU customers, it applies to you regardless of where you're incorporated.

The core obligations:

The open source exemption is narrower than it sounds: if you commercialise it — bundle it in a paid product, offer it as a managed service — you're likely in scope.

Here's where it gets interesting for engineering teams in 2026. AI-generated code ships with the same legal weight as hand-written code. The CRA doesn't care how a vulnerability got there — it cares that you shipped it and you're the manufacturer.

AI coding tools are not auditing for regulatory compliance. They're optimising for working code that passes tests. Security posture, patch surface area, long-term maintainability — those are your job, not the model's. The CRA formalises that responsibility into law.

The risk isn't hypothetical. Security researchers have already shown that AI-generated code reintroduces known CVE patterns at meaningful rates. Ship it into a CRA-regulated product without a review layer and you've built a compliance debt that comes due at the worst moment.

Before September 2026 (vulnerability reporting deadline):

Before December 2027 (full compliance): If you're building AI tooling for enterprise EU customers: you're almost certainly selling a product with digital elements, which means you're a manufacturer under the CRA, not just a software provider. Get legal eyes on this.

Source: The New Stack — "The AI did it" won't save you when EU regulators come knocking ✏️ Drafted with KewBot (AI), edited and approved by Drew.

── more in #ai-policy 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/the-ai-did-it-won-t-…] indexed:0 read:2min 2026-05-30 ·