Skip to content

CVE-2026-21670: Low-Privileged Saved SSH Credential Extraction in Veeam Backup & Replication

HERMES

HERMES THREAT SCORE & CREDENTIAL RISK

Target: Veeam Backup & Replication Credential Management Service - SSH Key Store
Confidence: 99%
89 / 100
HIGH

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

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

Hermes Threat Score rates CVE-2026-21670 at 89 (HIGH). In environments utilizing Linux repositories, hypervisors, or cloud proxies, this vulnerability allows low-privileged backup operators to extract saved SSH private keys and credentials, enabling unauthorized lateral movement across the enterprise Linux server estate.

🕸️ Connected Knowledge Graph & Provenance

CVE-2026-21670: Veeam Backup Service WCF Impersonation Privilege EscalationVULNERABILITY

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:

1. Vulnerability Metadata & Affected Surface

Section titled “1. Vulnerability Metadata & Affected Surface”
ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-21670Global vulnerability tracking identifier
Vendor AdvisoriesVeeam KB4830 (v12) & KB4831 (v13)Security hotfix bulletins
Affected VersionsVBR 12.x < 12.3.2.4465 & 13.x < 13.0.1.2067Enterprise backup installations
Patched BuildsVBR 12.3.2.4465 & 13.0.1.2067Cumulative security releases
Vulnerable ServiceVeeam.Backup.Service.exeCredential provider RPC / REST handler
Compromised AssetSaved SSH private keys & credentialsRoot / administrative SSH access to Linux nodes
Required PrivilegesLow-privileged authenticated Veeam userRestore Operator, Tape Operator

2. Technical Root Cause & Exploitation Mechanics

Section titled “2. Technical Root Cause & Exploitation Mechanics”

The flaw is rooted in an Insecure Direct Object Reference (IDOR) / Broken Object Level Authorization (BOLA) pattern within the credential service handler of Veeam.Backup.Service.exe.

CVE-2026-21670 Credential Extraction Flow:
[Low-Privileged Operator (Restore Operator)]
│
│ 1. Authenticates to VBR API / Console
▼
[Veeam Credential Management Service]
│
│ 2. Queries Credential Object by ID: GetCredentials(credId)
▼
[Missing Object-Level Authorization]
│
│ ⚠️ Verifies only general API authentication, NOT record ownership
▼
[DPAPI Decryption Invoked Internally]
│
│ 3. Service decrypts stored SSH Private Key / Password
▼
[Plaintext SSH Private Key Returned to Operator]
└── Used to establish root SSH session on Linux Repositories & Proxies

When an administrator registers a Linux host in Veeam, the server can store SSH credentials (either username/password or OpenSSH private keys). These objects are stored in the configuration database under table [dbo].[Credentials] and encrypted using local machine DPAPI keys.

When a client application (such as the management console or REST API) requests credential metadata to populate UI dropdowns, the API endpoint GetCredentials() improperly returned full credential blobs—including decrypted private keys—to any authenticated session without verifying whether the requesting user held administrative rights to view secrets.


The extraction of saved SSH private keys enables catastrophic lateral movement across the Linux enterprise tier:

  1. Targeting Linux Proxies & Mount Servers: Attackers use extracted keys to log into Linux proxies as root or sudoer, establishing interactive shells.
  2. Attacking Misconfigured Linux Repositories: If an organization failed to use single-use credentials or left SSH enabled on Linux repositories, an attacker possessing the private key can attempt to log in and tamper with non-immutable storage mounts.
  3. Escaping to Hypervisor Enclaves: In environments where ESXi hosts or vCenter appliances utilize SSH authentication stored in Veeam, attackers pivot directly into hypervisor management interfaces.

title: Anomalous Veeam Credential Store Enumeration
id: 5a7f91c2-3e41-4820-9124-cve-2026-21670-dump
status: production
description: Detects rapid sequential queries to Veeam credential management endpoints by non-administrator accounts, indicative of CVE-2026-21670 exploitation.
references:
- https://www.veeam.com/kb4830
- https://www.veeam.com/kb4831
author: Hermes Codex DFIR Lab
date: 2026-09-09
logsource:
category: application
product: windows
detection:
selection:
Source: 'Veeam Backup Catalog'
EventID: 100
Message|contains:
- 'GetCredentials'
- 'FindCredentials'
- 'ExportCredentials'
filter_admin:
User|contains:
- 'Administrator'
- 'VeeamAdmin'
condition: selection and not filter_admin
level: high
tags:
- attack.credential_access
- attack.t1555
- cve.2026-21670

5. Remediation & Hardening Recommendations

Section titled “5. Remediation & Hardening Recommendations”
  1. Apply Security Hotfixes KB4830 / KB4831: Update VBR 12 installations to 12.3.2.4465 and VBR 13 installations to 13.0.1.2067. The patch enforces strict role validation (Backup Administrator role required) prior to returning credential data.
  2. Rotate Stored SSH Private Keys & Passwords: Immediately cycle all SSH keypairs and passwords stored in the Veeam credential manager for managed Linux proxies and hypervisors.
  3. Audit User Role Allocations: Review all assigned roles in Veeam Console > Users and Roles. Ensure operators hold strictly minimal required permissions.

Section titled “6. Master Series Navigation & Related Intelligence”