Skip to content

CVE-2025-59469: Arbitrary File Write as Root by Operators in Veeam Backup & Replication

HERMES

HERMES THREAT SCORE & HOST PERMISSION ESCALATION RISK

Target: Veeam Backup Infrastructure Task Execution Service
Confidence: 97%
84 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 18 / 20
Threat Activity 16 / 20
Weaponization 17 / 20
Exposure 16 / 20
Prevalence 19 / 20
Impact 19 / 20
Exploit Maturity 17 / 20
Attack Chain Potential 19 / 20
⚖️ Divergence & Operational Rationale

Hermes evaluates CVE-2025-59469 with an HTS of 84 (HIGH). The vulnerability circumvents the principle of least privilege by allowing non-administrative backup and tape operators to command high-privileged daemons to write arbitrary files as root. By hijacking export routines, an operator can overwrite operating system configurations or inject malicious helper binaries.

🕸️ Connected Knowledge Graph & Provenance

CVE-2025-59469: Arbitrary File Write as Root by Operators in Veeam Backup & ReplicationVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTVeeam Backup & Replication
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

🔍 Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Veeam Backup & Replication documented in Hermes dossier.”

Supporting Verified Evidence:

MetricTechnical SpecificationOperational Impact
CVE IdentifierCVE-2025-59469Official NVD / MITRE identifier
Vendor AdvisoryVeeam KB4716Cumulative security update for VBR v13
Affected ComponentReporting & Tape Export SubsystemFile I/O orchestration routines
Affected ReleasesVBR 13.x $\le$ 13.0.1.180All deployment architectures
Patched ReleaseVeeam Backup & Replication 13.0.1.1071Recommended upgrade
Required PrivilegeBackup Operator or Tape OperatorLow-privileged authenticated role
Execution Contextroot (Linux) / SYSTEM (Windows)Arbitrary filesystem write

The structural flaw resides in the tape management and session logging handler (VeeamTapeService and associated binaries).

When requesting diagnostic exports, the API accepts an outputFilePath argument. The service fails to:

  1. Canonicalize and enforce that the path resides within the designated export sandbox.
  2. Impersonate the requesting caller’s security context before performing disk write operations.

Consequently, disk writes occur under the security context of the root master process.


Sigma Rule: Suspicious File Write by Veeam Tape Service

Section titled “Sigma Rule: Suspicious File Write by Veeam Tape Service”
title: Suspicious File Write by Veeam Tape Service
id: cve-2025-59469-veeam-tape-write
status: experimental
description: Detects file write operations outside standard directories by Veeam Tape daemons
references:
- https://www.veeam.com/kb4716
logsource:
category: file_event
product: linux
detection:
selection:
Image|endswith:
- '/VeeamTapeService'
- '/veeamsvc'
TargetFilename|startswith:
- '/etc/'
- '/usr/'
- '/var/spool/'
filter:
TargetFilename|startswith: '/var/log/veeam/'
condition: selection and not filter
level: high

  1. Deploy KB4716: Upgrade to Veeam Backup & Replication 13.0.1.1071 immediately.
  2. Mount Isolation: Configure dedicated partitions mounted with nosuid,noexec for all temporary and export directories.
  3. Audit Operator Roles: Audit and minimize assignments to the Backup Operator and Tape Operator roles.