Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

It's been a brutal few weeks. A developer laptop led to the largest theft in crypto history at Binance. LiteLLM was poisoned, again, on PyPI. PHP2Shell and Node2Shell hit PHP and Node.js, which together run a huge share of the web. And let's not forget eMudhra and the private keys that could be recovered in seconds. These incidents relied on familiar techniques and very little sophistication. Attackers moved fast, though, and the window between disclosure and exploitation is closing quickly.

If your organization collects personal information from California residents, you already know the California Consumer Privacy Act (CCPA) isn’t optional. What you may not fully appreciate yet is that application security for CCPA compliance isn’t really about checking boxes on a vulnerability scanner report. It’s about managing software risk at a level of rigor, continuity, and accountability that can hold up when regulators, auditors, or plaintiff attorneys come asking questions.

This post is based on Mackenzie's conversation with Abdel Sghiouar on The Secure Disclosure podcast. Listen to the full episode or watch below. If you give an agent the run of your cluster, it can trace a problem through every layer of the stack faster than any on-call engineer. But that same reach makes the agent worth hijacking.

Seven years after the General Data Protection Regulation came into force, organizations are still learning a hard lesson: GDPR compliance is a technical lesson as much as it is a legal one. Application security for GDPR compliance sits at the center of that reality, because the personal data GDPR protects lives in your software: your web applications, your APIs, your cloud-native services, your third-party integrations.

PHP2Shell is a pair of critical remote code execution (RCE) vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619. Both score 9.2 on CVSS v4.0, and either one can let an unauthenticated attacker run code on a server that handles PHP requests. Cloudflare reports that exploitation has started. PHP shipped fixes on October 21 in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older are out of support and won’t get an upstream release.

Aikido Security's AI Pentesting fits into the stack you already run. Even if you're committed to your current code and cloud security tools, you can add AI pentesting on top to catch the complex logic flaws deterministic tools miss.

Node.js shipped a security update on Wednesday for a flaw in how it decompresses Brotli data, a bug people are already calling Node2Shell (CVE-2026-111497). If an attacker can get a malicious payload in front of your app, the flaw can crash the process, leak part of its memory, or potentially let them run their own code. Who is affected: anyone running Node.js or Bun whose app decompresses Brotli data that an attacker could control.

Two critical remote code execution vulnerabilities have been found in PHP itself. Treat all versions as affected. ‍The vulnerabilities, CVE-2026-109618 and CVE-2026-109619, both have a CVSS v4.0 score of 9.2. The PHP security team will release fixes on October 21, 2026, at 16:00 CEST / 10:00 EDT / 07:00 PT. If you run PHP anywhere in your stack, please stay tuned for workarounds and patches. Be prepared to take action.