CVE-2025-46811: Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1 · Missing Authorization
Affects Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1Source CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · 11% EPSS · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 11.2% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 30 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by suse
, 91 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 12 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
SUSE Manager 4.3.15 - Code Execution
, 274 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
Until a fix is available, restricting network access to port 443 of the SUSE Manager server to trusted administrators only may reduce exposure.
Description
CVE-2025-46811 is a critical missing authorization vulnerability in SUSE Linux Manager containers and related images. It allows any unauthenticated user who can connect to port 443 of the SUSE Manager server to execute arbitrary commands as root on any client. This affects multiple SUSE Manager container images and server modules prior to specified patch versions. The vulnerability has a CVSS score of 9.8, indicating high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild at this time. Patch status is not confirmed as no patch links or vendor advisory details are provided.