Skip to content
Tech News
← Back to articles

The EU CRA's Real Question: What Shipped, and When Did You Know?

read original get Yubico YubiKey 5 NFC Security Key → more articles
Why This Matters

A maintainer's account of an AI-scale, extortion-backed vulnerability report (95 claims, 2-3 real, followed by a $100,000 demand) illustrates the triage burden that the EU Cyber Resilience Act is about to make a legal obligation rather than a volunteer's headache. From September 11, 2026, manufacturers selling products with digital elements into the EU must notify ENISA within 24 hours of learning an included vulnerability is being actively exploited. That turns 'what shipped, and when did you know?' into a compliance question every software vendor must be able to answer on the clock.

Key Takeaways
Worth a Look

Yubico YubiKey 5 NFC Security Key — The article opens with a GPG-signed disclosure report, and the YubiKey 5 NFC is the hardware key many maintainers use to hold their signing and authentication credentials off the laptop. It works over USB-A and NFC, so you can sign commits and log into project infrastructure from a desk or a phone. For anyone maintaining software that will fall under compliance scrutiny, keeping keys on dedicated hardware is a simple, durable upgrade.

See Yubico YubiKey 5 NFC Security Key on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

What a maintainer's disclosure inbox already knows about the question the EU Cyber Resilience Act is about to ask every software vendor.

Written by: Shane Warden, Principal Architect, ActiveState

Last year, someone submitted a vulnerability report to a security address for a free software project I help to review. The report followed our reporting guidelines, with a GPG signature and proper responsible disclosure ceremony, addressed only to the people who should have seen it.

It contained 95 vulnerabilities, purportedly. We took it seriously, because that security process exists for exactly this reason.

Yet something felt off, because how many human security researchers would compile a list 95 long and keep going instead of stopping at three or four and asking for a longer engagement.

Two or three of the 95 turned out to be real. That's a low percentage, and it didn't matter, because we still had to work through all 95 to find the two or three that did. Then came the second email: pay $100,000, or the report would go public with Heartbleed-style press.

The report itself was inflated. The threat behind it was not, because the blast radius of a disclosure like that is every deployment of the affected software an attacker can find by scanning the open internet for who's still running it.

I’m not the only person who’s seen this, and I think the problems open source maintainers are wrestling with now are the problems other enterprises will encounter very soon. The informal reality of volunteers becomes the operational reality of the entire software world.

On September 11, 2026, something adjacent to what I just described stops being a volunteer's problem and becomes a legal one for a very large number of companies.

The EU Cyber Resilience Act's reporting obligations take effect then: any manufacturer with a product with digital elements sold into the EU has to notify ENISA within 24 hours of learning a vulnerability in that product is being actively exploited, with a fuller report inside 72 hours.

... continue reading