Two simultaneous security shocks dominated the day: PHP shipped a pre-announced security release window after two critical remote-code-execution flaws (CVSS 9.2) were embargoed but effectively leaked when CVE hints and exploit chatter spread via LLMs and social posts - one exploit later retracted. The PHP security team preserved an orderly disclosure, but the real risk lies in who receives updates: only PHP 8.2-8.5 are supported, while PHP 8.1 and older are EOL. WordPress usage data shows 35.1% of WordPress sites run unsupported PHP and 16.46% still on 7.4, leaving a huge installed base exposed. Hosts and governments took sites offline; Cloudflare deployed WAF stopgaps; Node.js explicitly declared EOL versions affected by security releases, forcing an operational choice about whether to patch unsupported branches as Microsoft once did for XP.
A separate crisis exposed a deeper trust failure: eight intermediate emudhra (emSign) CA private keys were trivially small (values under 256), including one equal to 4, and had been trusted since a key ceremony on 30 April 2025. Browsers blocked those intermediates within hours of disclosure, Mozilla removed the root, and Go released updates hard-blocking the keys; about 30,000 certificates require migration. eMudhra blames a key-generation script flaw and misused labels despite HSM claims. There is no local patch for site owners - only distrust and trust-store updates - and many clients (curl on macOS, container images, IoT, old Go binaries) will remain vulnerable until rebuilt or updated.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.