Sweet Security Offers All Organizations Affected by HTTP2Shell Virtual Patching Protection at No Cost
The root-cause fix will take weeks; protection can't wait.
Security | Threat Detection | Cyberattacks | DevSecOps | Compliance
The Latest Cybersecurity News & Insights From Around The World
Hunt or be Hunted: HuntIQ Hunters Take on php2shell
Learn how Tanium put a fleet-wide PHP inventory in every Tanium Cloud tenant about eight hours after PHP shipped its php2shell fix.
PHP2Shell Vulnerabilities: What Happened, Who Is Affected and How to Respond
On 21 October 2026, two critical vulnerabilities in PHP, known collectively as PHP2Shell, prompted urgent security warnings from the UK’s National Cyber Security Centre (NCSC) and other cybersecurity authorities. Tracked as CVE-2026-109168 and CVE-2026-109619, both vulnerabilities carry a CVSS v4.0 score of 9.2 and could allow unauthenticated attackers to execute malicious code remotely on vulnerable PHP servers.
SANS 2026 Exposure Management Survey
The SANS 2026 Exposure Management Survey reveals a significant gap between adoption and effectiveness. While 91% of organizations have implemented exposure management, only 7% operate continuously, and just 15% report significant risk reduction. The biggest challenges aren’t a lack of security tools, but fragmented exposure data, incomplete asset visibility, unclear remediation ownership, and manual workflows.
Node2Shell (CVE-2026-111497): Why Server-Side Vulnerabilities Create Browser-Side Risks
Just days after the disclosure of two critical PHP vulnerabilities, another serious security flaw has emerged, this time affecting Node.js and the widely used Brotli compression library. Known as Node2Shell (CVE-2026-111497), the vulnerability can allow attackers to corrupt application memory by supplying specially crafted compressed data. Successful exploitation could result in application crashes, information disclosure, or remote code execution (RCE).
The Impact of AI on CVEs: Industry Challenges
Integrating artificial intelligence into cybersecurity has fundamentally changed vulnerability research – and not necessarily for the better. For decades, discovering and verifying Common Vulnerabilities and Exposures (CVEs) required deep technical expertise, creating a disciplined process that kept disclosure volume relatively manageable. Today, Generative AI has obliterated that barrier to entry.
PHP2Shell Breaks the Internet - The 443 Podcast - Episode 393
This week on the podcast, we dive into a pair of PHP vulnerabilities dubbed PHP2Shell and the chaos they caused through uncoordinated disclosure. After that, we discuss a certificate authority who's random number generator only goes to three digits before ending with law enforcement action around ShinyHunters ransomware negotiators.
Explaining PHP2Shell | Arctic Wolf Threat Brief
In this explainer from Arctic Wolf's Peter Ingebrigtsen, we break down what the PHP2Shell vulnerabilities are, how attackers are exploiting them, and the steps organizations should take now to reduce exposure. Arctic Wolf customers can use Aurora Exposure Management to identify affected assets and prioritize remediation, while the Aurora Agentic SOC helps detect and respond to post-exploitation activity such as webshell deployment, unauthorized command execution, persistence, and lateral movement.
OWASP Top 10 Kubernetes Security Risks Explained: Why Credentials Deserve a Closer Look
GitGuardian researchers reached 44 active Kubernetes clusters through leaked secrets, and 30% had been exposed for more than two years. Here’s how the OWASP Kubernetes Top 10 explains these Kubernetes security risks, and why K03, Secrets Management Failures, turns one leak into a chain.
How to patch PHP2Shell with free Aikido Images
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.