Unauthenticated service interruption via memory exhaustion
Published Aug 4, 2026 · Updated Aug 4, 2026
Memory exhaustion in Veeam Service Provider Console before 9.3 allows remote attackers to interrupt service without authentication. A remotely reachable operation consumes host memory until it is exhausted, but Veeam has not disclosed the affected endpoint, request field, or allocation path. No credentials or user interaction are required, and the documented consequence is loss of availability rather than data access or modification.
Summary
What happened
Memory exhaustion in Veeam Service Provider Console before 9.3 allows remote attackers to interrupt service without authentication. A remotely reachable operation consumes host memory until it is exhausted, but Veeam has not disclosed the affected endpoint, request field, or allocation path. No credentials or user interaction are required, and the documented consequence is loss of availability rather than data access or modification.
The record
- CVE
- CVE-2026-58067
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Veeam Software
- Product
- Veeam Service Provider Console
- Classifications
- CWE-789, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo