The stories that mattered most across all sources.
Two critical unauthenticated RCE flaws in PHP
PHP maintainers released fixes on 21 October for CVE-2026-109618 and CVE-2026-109619, both unauthenticated remote code execution rated CVSS 9.2. The highest risk is mod_php, where an unauthenticated request can trigger the flaw before any application code runs. Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and Krebs reported working exploits already circulating.
Why it matters: PHP runs a large share of the web, so this is a fleet-wide emergency patch across every PHP host, container image and managed platform. Treat unpatched internet-facing PHP as presumed compromised.
A certificate authority's keys were cracked in milliseconds
Cloudflare found eight eMudhra intermediate CA certificates whose private keys were catastrophically weak, letting anyone recover the signing key and forge a certificate for any domain. These intermediates chain to roots trusted by Mozilla, Microsoft, Apple and Chrome. Cloudflare deployed mitigations on 19 and 20 October, and eMudhra later said it will exit the global TLS certificate business.
Why it matters: Any system bundling these trust anchors is exposed to TLS interception until the certificates are distrusted. Update affected clients, review mTLS trust stores and container base images, and confirm certificate verification stays on.
A backdoored LiteLLM package and a Railway breach hit secrets
A malicious LiteLLM 1.107.0 was published to PyPI on 21 October with a credential stealer and a persistent backdoor that polled GitHub for commands. Attackers used stolen GitHub CLI credentials to bypass branch protection and build from a lookalike repo before PyPI removed it. The same day, Railway disclosed unauthorized access to systems holding customer environment variables, some decrypted, and told customers to rotate everything.
Why it matters: A single poisoned AI-gateway dependency runs on every Python process, and PaaS-stored secrets are a single point of compromise. Pin dependencies, verify provenance, and rotate credentials on any host that installed the bad version.
A court ordered Meta to pay 25 billion dollars over Cambridge Analytica
On 21 October a New Mexico court imposed 25 billion dollars in civil penalties on Meta in the state's Cambridge Analytica consumer-protection case, after a jury found about 43.9 million violations. The judge set the figure down from a much larger statutory maximum. Meta said it will appeal, and 48 other states had previously settled similar claims.
Why it matters: One of the largest privacy-related penalties to date raises the financial stakes of data-handling and consumer-protection failures, and keeps data governance a board-level question.
DHS ordered DeepSeek removed from federal civilian systems
On 19 October DHS posted an order banning federal civilian agencies from acquiring DeepSeek products and requiring removal of DeepSeek and DeepSeek-based third-party tools, citing the Federal Supply Chain Security Act. National-security and SCI systems are excluded, and agencies can seek exceptions.
Why it matters: A government supply-chain exclusion of a specific AI vendor raises model-provenance scrutiny that can cascade to contractors. Check whether any of your tools embed DeepSeek models, and track vendor-ban risk in AI procurement.