basicsecurity.net
Proof, not just disclosure.
Threats / Veeam / CVE-2022-26500
CVE-2022-26500 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Veeam Backup & Replication vulnerability

Veeam Backup & Replication contains an unauthenticated API access vulnerability allowing remote code execution through malicious code upload and execution.

Verdict

Today item, not a backlog item.

An unauthenticated remote attacker can exploit the Veeam Distribution Service to upload and execute arbitrary code, leading to complete system compromise. This vulnerability has been actively exploited in ransomware campaigns.

CISA KEV Yes · 2022-12-133Ransomware use Flagged3EPSS 0.05942 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-12-13), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.05942 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Veeam, Backup & Replication. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I identify the unauthenticated Veeam Distribution Service API endpoint exposed on the network.
Business
The organization's backup infrastructure is directly accessible without authentication controls.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft malicious input to the internal API functions to upload executable code to the system.
Business
Backup systems become a vector for unauthorized code deployment within the infrastructure.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute the uploaded malicious code with the privileges of the Veeam service.
Business
Attackers gain code execution on critical backup infrastructure, enabling lateral movement and data exfiltration.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence and deploy ransomware across the backup environment and connected systems.
Business
Backup and recovery capabilities are compromised, preventing disaster recovery and enabling widespread encryption attacks.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • 5 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.