RCE in Veeam Backup & Replication via interval/order parameter
CVE-2025-59470 is a command injection / remote code execution vulnerability in Veeam Backup & Replication Version 13. The flaw allows a user assigned the Backup Operator or Tape Operator role to execute arbitrary commands as the postgres user by supplying a malicious interval or order parameter to the application. NVD classifies the issue as CWE-77 and assigns CVSS v3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L. Affected versions are Veeam Backup & Replication 13 builds from 13.0.0.4967 inclusive up to 13.0.1.1071 exclusive; multiple sources also describe the affected range as 13.0.1.180 and earlier within the 13.x branch. Veeam states versions 12.x and older are not affected.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a minimal proof-of-exploitation for a command injection vulnerability in PostgreSQL’s pg_backup extension affecting PostgreSQL 15.x (<15.7) and 16.x (<16.3). Structure: - README.md: States affected versions and describes unsanitized user-supplied parameters in pg_backup leading to OS command execution as the PostgreSQL user. - exploit.py: Python script using psycopg2 to authenticate to a PostgreSQL instance (host "target", db "postgres", user "backup_operator") and call pg_backup() with a crafted argument that appends a shell command using ';'. The included payload attempts a bash reverse shell to 192.168.1.10:4444. - exploit.sql: Standalone SQL demonstrating the same injection technique, using curl to download and execute http://attacker.com/backdoor.sh. Capabilities: - Remote exploitation over the PostgreSQL protocol using valid credentials. - Arbitrary command execution on the database host via argument injection into pg_backup. - Demonstrated post-exploitation actions: reverse shell callback and remote script download/execute. Notable observables/fingerprintable targets: - Reverse shell endpoint: 192.168.1.10:4444 - HTTP payload host: http://attacker.com/backdoor.sh - Local paths used in payloads: /tmp and /dev/tcp/192.168.1.10/4444
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
42 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Veeam Backup & Replication RCE allowing Backup/Tape Operator role to execute code as postgres user.
Command injection vulnerability in Veeam Backup & Replication that could enable arbitrary code execution and potentially full system compromise for users with backup/tape operator access; not reported actively exploited.
A high-severity Veeam vulnerability that allows a privileged role (Backup or Tape Operator) to achieve remote code execution by supplying malicious parameters (interval/order), enabling attackers with post-compromise access to escalate impact within backup infrastructure.
A critical remote code execution vulnerability in Veeam Backup & Replication that allows users with Backup Operator or Tape Operator privileges to execute arbitrary code as the postgres user via network vectors, potentially leading to full compromise of the backup server.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.