Writing
Blog posts covering application security, infrastructure hardening, vulnerabilities, and incident response.
Latest Post
Two new Linux kernel LPE exploits (DirtyFrag and Copy Fail 2: Electric Boogaloo) abuse the esp4 and esp6 IPsec modules. Same class of threat as CVE-2026-31431. Here's what Magento operators need to do right now.
CVE-2026-31431 is a straight-line logic flaw in the Linux kernel's AF_ALG crypto API that's been exploitable on every major distro since 2017. Magento hosts are high-priority targets. Here's what you need to do right now.
GitHub accidentally included webhook secrets in HTTP headers between September 2025 and January 2026. Here's what happened, who's affected, and what you need to do about it.
How to guide on checking if your Magento 2 store is safe from the Polyshell vulnerability. And guidance on how to patch and secure your site if it is not.
Adobe's new monthly isolated patch approach for Magento creates maintenance burden. Here's how a community meta-package can help restore sanity to security patching.
Learn how to integrate Sansec Ecomscan into Magento 2 CI/CD pipelines to detect malware, enforce security patches, and secure build artifacts. Step-by-step guides for GitHub Actions and Bitbucket Pipelines included.
How to guide on checking if your Magento 2 store is safe from the Session Reaper (CVE-2025-54236) exploit. And guidance on how to patch and secure your site if it is not.
Approaches to simply deploying patches across a large inventory of Magento 2 deployments
Should you aim for 100% uptime across your servers? Or instead target fluid infrastructure where short lived nodes can spawn and die as required?
Have you explicitly disable the Magento 2 setup route in your web server configuration? The vast majority of sites scanned are showing this route as leaking your full Magento Version.