CVE-2026-58073: A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to impersonate a man...
A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to impersonate a managed agent andobtain that agent's credentials.
Security readout for executives and security teams
Plain-English summary
Veeam Service Provider Console has a critical authentication weakness that may let an unauthenticated network attacker pose as a managed agent and obtain that agent’s credentials. This could undermine trust in managed-agent operations. The supplied record does not clearly identify affected releases, so organizations should urgently compare deployments with Veeam’s advisory.
Executive priority
Treat this as an urgent validation-and-remediation issue because credential theft from a management platform could have broad operational consequences. Assign ownership immediately, inventory consoles, and consult KB4893. Do not assume every deployment is affected because the supplied version data is incomplete.
Technical view
CVE-2026-58073 is classified as CWE-288 and scored 9.5 under CVSS 4.0. Its vector indicates network reachability, no required privileges or user interaction, high attack complexity, and high confidentiality, integrity, and availability impacts. The described result is unauthenticated managed-agent impersonation and credential disclosure.
Likely exposure
Exposure is most likely where Veeam Service Provider Console manages agents and is network-reachable by potential attackers. Exact scope cannot be determined from the bundle: the affected version is listed only as “0,” with a default status of “unaffected.” Confirm deployment details against Veeam KB4893.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. High attack complexity may reduce reliability, but the lack of authentication and potentially severe credential impact still warrant urgent attention.
Researcher notes
The record supports an authentication-bypass or impersonation condition, but the bundle provides no root-cause details, affected-version range, fixed release, indicators of compromise, or exploitation evidence. The “0” version entry and default-unaffected status require confirmation from the vendor advisory before precise scoping.
Mitigation direction
Review Veeam KB4893 for confirmed affected versions and vendor-approved remediation.
Inventory all Veeam Service Provider Console deployments and their installed versions.
Follow the vendor remediation; the supplied bundle identifies no specific fixed release.
Initiate credential-exposure response procedures if managed-agent impersonation is suspected.
Validation and detection
Compare every deployed console version with the affected scope documented in KB4893.
Confirm vendor remediation has been applied using Veeam’s verification guidance.
Identify consoles reachable from untrusted networks or broadly accessible internal segments.
Review relevant logs for unexplained agent identity, authentication, or credential-access events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-288 · source CWE mapping
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.