Operations | Monitoring | ITSM | DevOps | Cloud

Express Ships a body-parser Fix for a Request DoS. Upgrade Now.

A denial-of-service bug that can take down a Node process with one crafted request is the kind of thing you want patched before you think about it again. Express just bumped body-parser to ^2.4.0, pulling in the fix for CVE-2026-111181, and the failure mode is a hard crash rather than a slow degradation. Scout Monitoring instruments Express out of the box, and a crash loop is exactly the kind of event that should show up on a dashboard the moment it starts.

Laravel Patches a TokenGuard Auth Bypass. Update Your 10.x Apps.

If your Laravel app authenticates API requests with a token, this one is worth a look today. Laravel just backported a TokenGuard fix to the 10.x line for CVE-2026-114509, and it closes an authentication bypass that needs nothing more than a cleverly shaped query string. Scout Monitoring instruments Laravel out of the box, so if you run an older app that’s still on 10.x, this is exactly the kind of change worth confirming lands cleanly in production. Watch it with Scout for free while you upgrade.

Rails 8.1.4.1 Is a Big Security Release. Upgrade This Week.

Rails 8.1.4.1 is a security point release, and it’s a substantial one. It carries around a dozen CVE-level advisories spread across Action View, Action Pack, and Active Support. There are no feature changes to weigh and no behavior most apps need to plan around, which makes this the easy kind of upgrade to justify: bump it this week. (The fixes were also backported to the 8.0 and 7.x series, so you don’t have to be on 8.1 to get them.)

CVE-2026-109518 APT vulnerability fixes available

Max Justicz discovered and responsibly disclosed a vulnerability in APT, the package manager used in Debian, Ubuntu, and derivative Linux distributions. The vulnerability has been assigned the identifier CVE-2026-109518 and has a severity of High. An on-path attacker who can manipulate the HTTP traffic between a system and an archive server can trigger the installation of an attacker-controlled.deb package file and obtain root privileges on the target system.

MongoDB's Node Driver 7.8.0 Patches Two Real Security Issues

If your Node app talks to MongoDB through the official mongodb driver, 7.8.0 is worth upgrading to before your next routine dependency pass. It’s a minor version by the number, but it carries two security fixes, and one of them changes how a feature you may already be using behaves.

The Jolokia Problem: Eight CVEs, One Door in Apache ActiveMQ

The Apache ActiveMQ Jolokia endpoint has been the route to remote code execution in three separate years. In 2023, it was reflection into the JVM. In 2024, a default configuration left it without a login. In 2026, it was the broker's own management operations, patched in March, exploited in April, and reopened three more times by summer.

Who Really Screwed Up the PHP2Shell Security Crisis?

The PHP2Shell vulnerability triggered a massive cybersecurity crisis. But the real story isn't just about the PHP security flaw. It's about who broke the rules, who was responsible, and whether one controversial decision made everything worse. In October 2026, researchers uncovered critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) that threatened websites and applications across the internet. As security teams scrambled to prepare patches, the coordinated disclosure process began falling apart.

PHP2Shell Exposed a Bigger Problem. Is Your IT Team Ready for the Next Threat?

A critical security vulnerability can put an entire business at risk before IT teams have even established where the problem lies. For CIOs, that means needing immediate answers about which systems are exposed, how essential business services could be affected and how quickly their teams can get ahead of the threat. That was the challenge facing organizations on October 21, when two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, emerged.