Blog
-
Inside the Binance and Polymarket breaches: five trust boundaries, and how to hold each one
The 29 October 2026 incidents at Polymarket and Binance did not break any cryptography. A vendor script and, reportedly, an engineer's laptop were trusted further than they should have been. A walk through both attacks as five trust boundaries, with the server and code controls that hold each one, an hour-by-hour response plan, and a script audit tool.
-
Who shipped what, and when: how the October 2026 fixes travelled from upstream to your stack
The October 2026 fixes for PHP, Node.js, BIND, Java and the kernel did not reach every system at once. A layer-by-layer tracker of who shipped what and when, from upstream projects to distributions, cPanel and CloudLinux, Docker images and libraries, and how to verify each layer.
-
One compromised CA, many trust stores: what the October 2026 Node.js, Java and BIND releases mean for your applications
Eight eMudhra intermediate CAs were blocked after a key compromise, and the fix reached browsers days before it reached Node.js and Java. Where trust lives inside your application, the Node.js fixes not covered last time, Java's JSSE alert and the BIND cases that concern developers.
-
PHP2Shell for developers: what the October 2026 PHP and Node.js fixes mean for your code, containers and CI
PHP2Shell runs before your application code, so no input validation can stop it, but your images, worker processes and settings decide how long you stay exposed. A developer's reading of the 21 October PHP and Node.js releases.
-
Patched runtime, unpatched code? Reading the 2026 PHP and Node.js fixes as a developer
Upgrading PHP and Node.js closes the 2026 vulnerabilities, but several of them point at coding patterns worth changing too. A layer-by-layer reading with a checklist for your code and pipeline.