Operations | Monitoring | ITSM | DevOps | Cloud

CVE-2026-74580 is a high-severity Linux kernel bug in vhost, the subsystem that accelerates I/O for virtual machines. It gives a local user a reliable path to root on the host, and in some VM setups it lets a guest write into host memory. The CVE record has existed since August 21, 2026, but the full technical write-up, nicknamed "Vghost", only went public on October 12. It came with working exploit demos for both a local root escalation and a VM escape.

On 7 October 2026, Daniel Stenberg published a blog post describing a plan to release a new version of curl on 14 October 2026 in order to address 22 known security vulnerabilities. These vulnerabilities have varying severities, with a single vulnerability assessed as high (CVE-2026-92392), while the others have a low or medium severity. The curl maintainer has coordinated with downstream vendors, including Ubuntu, under embargo and the vulnerabilities have been publicly disclosed on the planned date.

Avantra monitors SAP security patch status across entire landscapes, checking each newly published SAP HotNews note against every managed system and tracking which systems still need it. It covers the patch side of SAP vulnerability management, which is a different job from code-level vulnerability scanning.

✓ operational truth Operational risk is no longer limited by the ability to find vulnerabilities. It is limited by the ability to prioritize them by business exposure and to act on the large share that cannot be patched at all. Autonomous IT changes this by mapping findings to applications and owners, automating the work around the patch, and proposing evidenced mitigations where no patch exists.

Last updated: October 9, 2026 A zero-day vulnerability may be unknown, but its effects often are not. Exploitation can leave behind observable changes: a new privileged account, an altered management setting, an unexpected file, a modified access rule, or configuration drift from an approved baseline. That makes zero-day configuration monitoring an important part of a defense-in-depth strategy.

SAST vs SCA vs DAST vs IAST: a clear breakdown of what each scan finds, when to run it, and how to combine them across your SDLC. Most AppSec teams don't run one type of scan - they run several, at different points in the pipeline, because no single tool sees the whole picture. This article breaks down SAST vs SCA vs DAST vs IAST: what each one actually tests, where it fits in the software development lifecycle (SDLC), and how to combine them without duplicating effort or drowning developers in findings.

Compare LLM vulnerability scanners with AI SAST on precision, recall, speed, cost, and consistency to choose the right AI security approach.

Recent findings from Anthropic’s Project Glasswing offer a useful indication of where vulnerability discovery may be heading. Anthropic reported that it and its partners had used Claude Mythos Preview to identify more than 10,000 high- or critical-severity vulnerabilities across the software they reviewed. More significantly, Anthropic reported that the bottleneck had shifted from finding vulnerabilities to having the capacity to verify, disclose, and patch them.