CVE Intelligence
Critical Injection

CVE-2026-21669 — Code Injection in Veeam Backup and Replication

A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.

Published Mar 12, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.2% (30-day exploitation probability)+10
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.19%
ahead of 67% of scored CVEs · Oct 14, 2026
Affects
Veeam
Backup and Replication and 1 more
CVSS base
9.9
Critical · 2 source(s)
Prioritization reference: 10.0 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Veeam Backup and Replication, Veeam Veeam Backup & Replication).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Veeam Backup and Replication ≥ 13.0.1 and < 13.0.1 Vulnerable CVE Program (cve.org) e CISA ADP
Veeam Veeam Backup & Replication ≥ 13.0.0.496 and < 13.0.1.2067 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 3.1 Critical — — hackerone via CVE Program (cve.org) e CISA ADP
9.9 CVSS 3.1 Critical 3.1 6.0 support@hackerone.com via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: support@hackerone.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · veeam/backup and replication
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 9.9
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Mar 12, 2026 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Veeam
every CVE for this vendor
Injection
same class
CWE-94
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-93026 Missing Authorization in Veeam Backup and Replication 8d
  • CVE-2026-58069 Path Traversal in Veeam Backup and Replication 8d
  • CVE-2025-64393 Deserialization of Untrusted Data in Veeam Backup and Replication 8d
  • CVE-2026-44963 Deserialization of Untrusted Data in Veeam Backup and Replication Jun 9, 2026
  • CVE-2026-32997 A vulnerability allowing an authenticated user with the Backup Administrator role to… May 28, 2026
  • CVE-2026-32996 Insertion of Sensitive Information into Log File in Veeam Backup and Replication May 28, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-21669 is "Code Injection in Veeam Backup and Replication", rated Critical. It affects Backup and Replication (Veeam); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.9 describes technical severity. EPSS 1.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.