Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On Friday morning, March 21, 2025, at 9:00 a.m. UTC, a security advisory identified as CVE-2025-29927 was published. It cited a critical 9.1 severity vulnerability for mainstream Next.js applications. Next.js versions considered vulnerable: We urge all developers to upgrade and deploy the latest version of Next.js that carries a fix to avoid suffering critical authorization bypass and other middleware logic circumvention.

On March 17th, 2025, security researchers confirmed active exploitation of Apache Tomcat’s recently disclosed vulnerability, CVE-2025-24813. Publicly disclosed on March 10th, the earliest signs of exploitation were observed on March 12th, with attackers leveraging the flaw just 30 hours after disclosure. This vulnerability enables Remote Code Execution (RCE) and information disclosure by exploiting Tomcat’s request-handling mechanism.

Traditional vulnerability management is broken. It is ineffective. The process of scanning for software vulnerabilities, prioritizing based on CVSS scores, and fixing what you can has become an endless patch cycle. The need for a better approach is clear. Different scanning tools are creating millions of alerts, obscuring critical risks within the noise. Organizations need to go beyond finding and patching vulnerabilities and opt in to a more effective approach to managing exposures.