Security readout for executives and security teams
Plain-English summary
This critical Veeam Service Provider Console flaw can let a low-privileged, network-based attacker write arbitrary files to the management server. Successful abuse could result in remote code execution and compromise the server’s confidentiality, integrity, and availability. The supplied evidence does not establish which real-world releases are affected.
Executive priority
Assign immediate ownership and determine exposure now. Prioritize affected, externally reachable, or broadly accessible management servers for vendor remediation and compromise review. Do not delay solely because active exploitation is unconfirmed; the potential outcome is full management-server compromise.
Technical view
CVE-2026-58072 is an arbitrary-file-write vulnerability associated with path traversal (CWE-22). Its CVSS 4.0 vector indicates network access, low attack complexity, an additional attack prerequisite, low privileges, and no user interaction. A successful attack may escalate to remote code execution with high impact across affected systems.
Likely exposure
Potential exposure is limited to Veeam Service Provider Console management servers running an affected release and reachable by a low-privileged attacker. The bundle lists version “0” with a default unaffected status, which is insufficient to identify affected production builds. Confirm applicability directly through Veeam KB4893.
Exploitation context
The bundle does not show CISA KEV inclusion and provides no cited evidence of active exploitation or a public exploit. Exploitation nevertheless appears potentially practical because the vector indicates network reachability, low complexity, low privileges, and no user interaction, although an additional prerequisite must be satisfied.
Researcher notes
The central claim is arbitrary file write leading to remote code execution, categorized as CWE-22. The CVSS vector includes AT:P, but the bundle does not explain the prerequisite. Affected-version data is incomplete, and no patch details, indicators of compromise, exploit maturity, or attack-chain specifics are supplied.
Mitigation direction
- Consult Veeam KB4893 to identify affected builds and follow the vendor-prescribed remediation.
- Restrict management-server access to trusted administrative networks while applicability and remediation are assessed.
- Remove unnecessary VSPC accounts and minimize privileges for remaining users.
- Monitor for unexpected file writes and suspicious processes on the management server.
- Treat access restrictions as temporary risk reduction, not a substitute for vendor remediation.
Validation and detection
- Inventory all Veeam Service Provider Console management servers and record their exact builds.
- Compare installed builds and configurations with the applicability information in Veeam KB4893.
- Verify vendor-prescribed remediation is installed or configured on every affected server.
- Review file-integrity and process telemetry for unexplained changes on management servers.
- Confirm management interfaces are not reachable from unnecessary or untrusted networks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-58072 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——hackeroneVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.veeam.com/kb4893CVE reference, hackerone
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.