CVE-2025-59470 Overview
CVE-2025-59470 is a critical command injection vulnerability affecting Veeam Backup & Replication. This vulnerability allows a Backup Operator to perform remote code execution (RCE) as the postgres user by sending a malicious interval or order parameter. The flaw stems from improper neutralization of special elements used in a command (CWE-77), enabling authenticated attackers with Backup Operator privileges to execute arbitrary commands on the underlying system.
Critical Impact
Authenticated attackers with Backup Operator role can achieve remote code execution as the postgres user, potentially compromising backup infrastructure integrity and accessing sensitive backup data across the enterprise.
Affected Products
- Veeam Backup & Replication (all vulnerable versions)
Discovery Timeline
- 2026-01-08 - CVE-2025-59470 published to NVD
- 2026-01-14 - Last updated in NVD database
Technical Details for CVE-2025-59470
Vulnerability Analysis
This command injection vulnerability exists in Veeam Backup & Replication's handling of user-supplied parameters. The vulnerability is exploitable over the network without requiring user interaction, though it does require the attacker to have authenticated access with Backup Operator privileges. Despite the high privilege requirement, the vulnerability's scope extends beyond the vulnerable component, meaning successful exploitation can impact resources managed by other security authorities.
The impact of successful exploitation is severe, with high confidentiality and integrity impact allowing attackers to read sensitive data and modify system configurations. The vulnerability also affects system availability, though to a lesser degree. The changed scope characteristic indicates that compromising the Veeam application can lead to broader infrastructure compromise.
Root Cause
The root cause of CVE-2025-59470 is improper neutralization of special elements used in a command (CWE-77). The application fails to properly sanitize or validate the interval and order parameters before incorporating them into system commands. This allows attackers to inject malicious command syntax that is subsequently executed by the postgres user context.
The vulnerability exists because user-controlled input is passed directly to command execution functions without adequate input validation or output encoding. When the application constructs commands using these parameters, an attacker can break out of the intended command structure and inject arbitrary commands.
Attack Vector
The attack is executed over the network by an authenticated user with Backup Operator privileges. The attacker crafts a malicious request containing specially formatted interval or order parameters that include command injection payloads. When the vulnerable endpoint processes this request, the injected commands are executed with the privileges of the postgres user.
The attack flow involves:
- Authenticating to the Veeam Backup & Replication console with Backup Operator credentials
- Identifying the vulnerable endpoint that accepts interval or order parameters
- Crafting a malicious parameter value containing command injection syntax
- Submitting the request to trigger command execution
- Achieving code execution as the postgres database user
The vulnerability is particularly dangerous in enterprise environments where Veeam Backup & Replication manages critical backup operations across multiple systems. Compromise of the postgres user can lead to access to backup metadata, modification of backup jobs, and potential lateral movement within the backup infrastructure.
Detection Methods for CVE-2025-59470
Indicators of Compromise
- Unusual process execution originating from the postgres user account outside of normal database operations
- Unexpected network connections initiated by postgres or Veeam-related processes
- Anomalous command-line arguments containing shell metacharacters in Veeam-related logs
- Suspicious modifications to backup jobs or configurations by Backup Operator accounts
Detection Strategies
- Monitor Veeam Backup & Replication logs for requests containing unusual characters in interval or order parameters
- Implement application-layer firewall rules to detect command injection patterns in HTTP requests
- Enable detailed audit logging for all Backup Operator activities within the Veeam console
- Deploy endpoint detection rules to identify command execution chains originating from postgres processes
Monitoring Recommendations
- Review access logs for Backup Operator accounts and correlate with unusual system activity
- Implement real-time alerting for postgres user executing shell commands or scripts
- Monitor for unauthorized changes to backup configurations or job schedules
- Establish baseline behavior for Veeam services and alert on deviations
How to Mitigate CVE-2025-59470
Immediate Actions Required
- Apply the security patch from Veeam immediately by following the guidance in Veeam Knowledge Base Article KB4792
- Review and audit all accounts with Backup Operator privileges, removing unnecessary access
- Implement network segmentation to restrict access to Veeam management interfaces
- Enable enhanced logging and monitoring for all Veeam Backup & Replication activity
Patch Information
Veeam has released a security update to address this vulnerability. Administrators should consult the Veeam Knowledge Base Article KB4792 for detailed patching instructions and updated software versions. It is critical to apply this patch as soon as possible given the severity of the vulnerability and its potential impact on backup infrastructure.
Workarounds
- Restrict network access to Veeam Backup & Replication management interfaces using firewall rules
- Implement strict role-based access control and minimize the number of Backup Operator accounts
- Enable multi-factor authentication for all Veeam administrative access where supported
- Monitor and audit all Backup Operator activities until patching can be completed
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


