Tuesday, May 19, 2026

Today's Security Snapshot

Critical vulnerabilities, curated daily for security professionals

🎯 SSCV Profile

See how vulnerabilities affect your specific environment

CRS uses the System Security Context Vector (SSCV) Framework v1.0 to adjust CVSS scores based on your system's exposure level, network position, and business criticality. Learn more about SSCV Framework

Risk scores will be adjusted based on your selected environment

Today's Security Brief

Tuesday's disclosures center on Microsoft Azure Local, SGLang AI runtimes, and WordPress, with multiple remote code execution flaws affecting widely deployed enterprise and developer infrastructure. The brief covers 10 critical CVEs (up 233% from yesterday's 3) and 35 high-priority vulnerabilities (up 52% from 23). Notable issues include CVE-2026-42822 (CVSS 10) in Azure Local Disconnected, CVE-2026-27130 (CVSS 9.9) in Dokploy deployment platform, and three SGLang multimodal runtime flaws (CVE-2026-7301, CVE-2026-7302, CVE-2026-7304). Attack patterns skew toward RCE and unauthenticated access against cloud orchestration, AI inference services, and WordPress ecosystems. No vendor patches are currently available across this batch, requiring compensating controls and exposure reduction as the primary near-term posture.

  • Microsoft Azure Local Disconnected hit with CVE-2026-42822 at maximum CVSS 10 severity
  • Critical CVE count rose 233% day-over-day, from 3 to 10
  • High-priority CVE count rose 52% day-over-day, from 23 to 35
  • Remote code execution dominates, with SGLang AI runtime (3 CVEs), Dokploy, lwIP, and WordPress all affected
  • Patch availability sits at 0% across the day's critical and high disclosures
  • Two actively exploited CVEs in the wild: Cisco Catalyst SD-WAN (CVE-2026-20182) and Microsoft (CVE-2026-42897)

Immediate action: Prioritize exposure reduction for Azure Local Disconnected, Dokploy, SGLang inference endpoints, and WordPress deployments, and verify Cisco Catalyst SD-WAN and affected Microsoft systems against the two actively exploited CVEs. With no vendor patches yet published for the critical batch, apply network segmentation, restrict management interface exposure, and monitor for indicators tied to the listed CVE IDs until fixes are released.

💡 Tip: Swipe CVE cards left to ⭐ star, right to ❌ remove

Section Navigation