Saturday, May 30, 2026 Archive

Archived Security Snapshot

Critical vulnerabilities, curated daily for security professionals

Archived Security Brief

Self-hosted deployment and container management platforms dominated Saturday's disclosures, led by a cluster of Dokploy PaaS vulnerabilities and exposed Docker management interfaces. The day brought 18 critical CVEs (CVSS 9.0+), down 5% from the prior day's 19, alongside 63 high-priority CVEs, up 9% from 58. CVE-2026-45631 (CVSS 10) and several companion flaws in Dokploy PaaS headline the critical set, joined by CVE-2026-45625 (CVSS 9.9) in the Arcane Docker container management interface and CVE-2026-10042 (CVSS 9.8) in the manga-image-translator API server. The concentration in PaaS control planes, container orchestration, and exposed management APIs points to remote code execution and authentication bypass risk on internet-facing developer and operations infrastructure. No patches were available at disclosure for the critical issues, so affected operators should prioritize access restriction and network isolation while fixes are pending.

  • Dokploy PaaS accounts for several critical CVEs including CVE-2026-45631 at the maximum CVSS 10, affecting self-hosted deployment control planes
  • Critical CVEs totaled 18, a 5% decrease from the prior day's 19
  • High-priority CVEs rose to 63, a 9% increase from 58 the prior day
  • Container and platform management interfaces are central, with CVE-2026-45625 (CVSS 9.9, Arcane Docker) and CVE-2026-10042 (CVSS 9.8, manga-image-translator API) exposing RCE and auth-bypass paths
  • Patch availability stands at 0% for the disclosed critical issues, leaving exposed Dokploy, Docker, and Mautic (CVE-2026-9558, CVSS 9.9) deployments reliant on access controls
  • Five CVEs carry confirmed active exploitation, including Palo Alto Networks PAN-OS (CVE-2026-0257) and the LiteSpeed cPanel plugin (CVE-2026-48172)

Immediate action: Prioritize self-hosted Dokploy PaaS, Arcane Docker, and other exposed container management interfaces, restricting network access and enforcing authentication on management endpoints while vendor patches remain unavailable. Separately, expedite remediation of the actively exploited Palo Alto Networks PAN-OS and LiteSpeed cPanel plugin flaws where vendor fixes exist. With 0% patch availability for the critical set, treat isolation and monitoring as the primary near-term controls.

How to read this brief

CVSS score (e.g. 9.1) β€” severity from 0–10. Red marks critical (9+), orange high (7–8.9).

Exploitability β€” how hard the flaw is to attack, read from the CVSS vector:

  • Network / Adjacent / Local / Physical β€” how close an attacker must get. Network means reachable over the internet.
  • No / Low / High privileges β€” the access they need first. No privileges means no login required.
  • No interaction / User interaction β€” whether a victim has to do something (open a file, click a link). No interaction means fully automatable.

The lower the bar on all three, the easier to exploit at scale β€” β€œNetwork Β· No privileges Β· No interaction” is the worst case: hit from anywhere, no credentials, no victim action.

Actively exploited β€” confirmed under attack in the wild (CISA’s Known Exploited Vulnerabilities catalog). Prioritize these regardless of score.

EPSS Β· Nth percentile β€” FIRST.org’s estimated chance a flaw is exploited within 30 days. We flag it only in the top 10% β€” a statistical signal it’s unusually likely to be targeted, separate from whether attacks are confirmed.

πŸ’‘ Tip: Swipe CVE cards left to ⭐ star, right to ❌ remove

Section Navigation