
The vulnerability-at-scale problem is organizational, not technical, which means it will survive any single policy intervention. End-of-life systems stay in production because rip-and-replace costs exceed the perceived breach risk; liability rules change that calculus only if enforcement is swift and penalties exceed upgrade costs — a political question, not a cyber one.
The NCSC's framing of 'technical debt' is accurate but masks the real constraint: a critical infrastructure operator that patches 500 vulnerabilities per quarter will still be behind by 200 next quarter if vendors are releasing at current acceleration rates.
The NCSC's timeline compresses the threat window from theoretical to operational: if China and Russia are weaponizing AI for cyber operations by 2028, UK critical infrastructure faces 18-24 months to close a vulnerability gap that vendors are now exposing faster than defenders can patch.
The mechanism is not sophistication — it is scale. The Linux kernel alone patched over 1,000 vulnerabilities last month; major vendors are shipping hundreds per update. Unpatched systems remain the vector, which means the binding constraint is not technology but organizational will to upgrade and retire end-of-life systems.
Watch whether the government's consultation on product-liability rules (announced in the budget) translates to enforcement timelines — if vendors face liability only after a breach, the incentive to accelerate patching remains voluntary.
Has the NCSC identified specific critical-infrastructure sectors or operators running unpatched systems at scale, or is the 'unprecedented rise' warning based on vulnerability-discovery trends alone?
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.