Featured Posts
All Posts

Security
May 26, 2026
CVE-2026-44573, CVE-2026-44577, CVE-2026-44572: Three Next.js Vulnerabilities Affecting EOL versions
Three New Next.js CVEs: Middleware Bypass, Image DoS, and Cache Poisoning in EOL Versions. Here is what each one does, who is exposed, and how to resolve them.
Javier Perez

Compliance
May 26, 2026
68% of Codebases Contain License Conflicts and AI-Generated Code Is Making It Worse
The 2026 OSSRA report documents the largest year-over-year increase in license conflicts in 11 years of data. The driver is AI-generated code — and most organizations are not evaluating it for IP risk.
Taylor Corbett

Thought Leadership
May 26, 2026
The Verification Bottleneck: Why AI Found 12 OpenSSL Zero-Days While Curl Killed Its Bug Bounty
The same AI capability that delivered 12 of 12 verified OpenSSL zero-days also killed the curl bug bounty program. Verification — not discovery — is now the bottleneck defining open source security.
Taylor Corbett

Security
May 22, 2026
Package Override Kill Switches: npm, pnpm, Yarn, Maven, Gradle & NuGet
A copy-paste reference for emergency dependency control across every major package manager — plus what to do when the only safe version of a component is one upstream no longer ships.
Greg Allen

Thought Leadership
May 21, 2026
Securing End-of-Life Software in Kubernetes: A Platform Team’s Playbook
A Platform Team's Playbook for When Upgrading Isn't an Immediate Option
Justin Gorny

Security
May 20, 2026
Apache Tomcat May 2026 Security Release: 7 CVEs Affect Tomcat 8.5
How Apache's May 10 release impacts an EOL version the official security page no longer documents
Greg Allen

Thought Leadership
May 20, 2026
Node.js Collaboration Summit London 2026: HeroDevs Trip Report
What Node.js’s new release strategy and rising AI vulnerability noise mean for security, sustainability, and long-term support.
Marco Ippolito

Thought Leadership
May 19, 2026
What Is "AI Slop" in Security? A Plain-Language Guide to AI-Generated Vulnerability Reports
How AI-generated vulnerability noise is overwhelming maintainers—and reshaping the future of open source security.
Taylor Corbett

Security
May 18, 2026
CVE-2026-42945: NGINX Rift Heap Buffer Overflow Hits Ingress NGINX
How the “NGINX Rift” vulnerability creates an unauthenticated RCE risk for retired Ingress NGINX deployments.
Greg Allen

Compliance
May 18, 2026
Spring AI 2.0 Is Coming Soon. Your Boot 4.0 Migration Does Not Have to Start Tomorrow.
Spring AI 2.0 GA is scheduled for May 28. Here is what teams on Spring Boot 3.x need to know about the Boot 4.0 requirement, the real migration scope, and how to approach the upgrade without putting production at risk.
Taylor Corbett
.png)
Security
May 15, 2026
Spring Boot Managed Dependencies Still Get CVEs After EOL: May 2026 Patch Round-Up
24 upstream CVEs landed across Tomcat, Netty, Thymeleaf, Jetty, and pgjdbc in a single month — every one reachable through the Spring Boot managed-dependency BOM on at least one EOL line.
Erik Weibust

Security
May 15, 2026
Angular v19 Goes EOL May 19. Angular 22 Is Coming the Same Month. Here Is How to Navigate Both.
Angular v19 reaches end of life on May 19, 2026. Angular 22 is expected to ship around the same time. For enterprise teams, the overlap of an EOL deadline and a new major release is real pressure — and it is manageable if you plan for it correctly.
Taylor Corbett

Security
May 15, 2026
Spring Framework April 2026: 3 Web Stack DoS and Cache Poisoning CVEs
How a single April 17 release addressed three independent denial-of-service vectors in the Spring 5.3, 6.1, 6.2, and 7.0 web stack, with two of those branches receiving fixes only on commercial subscriptions
Greg Allen

Security
May 14, 2026
Angular EOL Security in 2026: AI Tooling Is Widening the Gap
Why the gap between modern Angular AI tooling and EOL versions is becoming a critical security risk.
Shelby Kelley
.png)
Security
May 13, 2026
Mini Shai-Hulud: Another npm Supply Chain Worm, and Why "Just Update" Isn't the Answer
The TanStack compromise shipped 84 malicious package versions with valid SLSA Build Level 3 provenance attestations. Cryptographic signing worked exactly as designed, and that's the problem.
Allison Vorthmann


