Since 11 September 2026, actively exploited vulnerabilities must be reported within 24 hours.Find your CRA gaps
Real-life story 2The thermostat that went cold, January 20163 min read

3 a.m. in January. The radiator under the window was cold.

How one routine update left homes without heat, and what the Cyber Resilience Act now asks of every company that ships updates.

The facts

What happened

A bug introduced in a December software update for a popular smart thermostat drained the batteries in some units. It only showed up about two weeks after the update had reached homes.

What it caused

Affected thermostats shut off heating in January, leaving some homes cold overnight. The manufacturer released a fix and told users how to restart and recharge their devices by hand.

What the CRA now asks

Protect the integrity of programs (Annex I, Part I (2)(f)) and the availability of essential functions (Annex I, Part I (2)(h)); securely distribute updates (Annex I, Part II (7)). A staged rollout with a stop button is our recommended way to get there, not a legal requirement in itself.

Source: The Register, "Nest thermostat owners out in the cold after software update cockup", 14 January 2016

The story

Birgit was eighty-one and lived alone, and her son had put in a smart thermostat that Christmas so he could keep an eye on her heating from his flat across town. She liked it. It glowed a soft orange when the heat came on, and she said goodnight to it, which made him laugh.

One night in January she woke at three and could see her breath. The radiator under the window was cold. The little screen on the wall was dark. She did not want to wake anyone, so she found a second blanket and sat up in bed with her hands tucked under her arms, waiting for morning.

What neither of them knew was that the thermostat had been dying for two weeks. Back in December it had quietly received an update, the same kind of automatic change your phone gets overnight, and hidden inside that update was a mistake that drained the battery a little at a time. The update had gone to homes everywhere at once, and by the time anyone noticed, it could not be taken back. In the morning her son drove over and followed instructions from the internet to restart and recharge it by hand, and Birgit made coffee and told him she had been fine, which was not quite true.

Under the Cyber Resilience Act, products must protect the functions people depend on, and updates must be distributed securely. In practice that means sending an update to one home in a hundred first, then one in ten, with someone watching in between, the way a cook tastes the soup before serving the whole room. The mistake shows up in a few hundred homes, the update stops, and Birgit sleeps through the night.

The people and scenes are illustrative. The incident and its facts are real.

The system that would have caught it

3. Ship updates safely

Every update is digitally signed, so products only accept the real thing. Updates go out in stages: a few homes, then more, then everyone.

How the system works

Could you do this today?

Could you stop a bad update halfway through the rollout?

If it applies, how ready are we?

Six yes-or-no questions, two minutes. Your no's come back in the order to fix them.

Not sure the CRA applies to your product? Check that first
Find your CRA gaps (6 questions, 2 min)

More stories