LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26500: Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote a...

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers to upload and execute arbitrary code.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-26500 affects Veeam Backup & Replication versions 9.5U3, 9.5U4, 10.x, and 11.x. A remote authenticated attacker could reach internal API functions, upload code, and execute it. Because backup systems hold sensitive recovery data and privileged access, compromise can materially affect recovery, confidentiality, and operations.

Executive priority

Treat this as an urgent remediation item for backup infrastructure. CISA KEV status means known exploitation exists, and successful compromise could undermine restoration capability during an incident.

Technical view

The issue is CWE-22 improper pathname limitation in Veeam Backup & Replication. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8. Public sources describe remote authenticated access to internal API functions leading to arbitrary code upload and execution.

Likely exposure

Organizations running the named Veeam Backup & Replication versions are the relevant exposure set. Risk increases where management services are reachable by broad internal networks, remote access paths, or accounts with weak controls.

Exploitation context

CISA lists CVE-2022-26500 in the Known Exploited Vulnerabilities catalog, so treat exploitation as confirmed. The provided sources do not include exploit mechanics, observed actor details, or specific campaign information.

Researcher notes

Evidence supports authenticated remote code execution via internal API access, but the source bundle does not provide exploit details or precise fixed versions. Validation should focus on version inventory, vendor advisory status, exposure review, and compromise assessment.

Mitigation direction

  • Check Veeam KB4288 and apply vendor-directed updates or workarounds.
  • Prioritize remediation on internet-reachable or widely reachable Veeam servers.
  • Restrict Veeam management and API access to trusted administrative networks.
  • Review and tighten authenticated access to Veeam administration functions.
  • Investigate affected systems before reconnecting if compromise is suspected.

Validation and detection

  • Inventory Veeam Backup & Replication versions across all environments.
  • Confirm whether any 9.5U3, 9.5U4, 10.x, or 11.x systems remain.
  • Verify vendor guidance from KB4288 has been applied.
  • Review authentication, upload, service, and execution logs for anomalies.
  • Confirm exposure paths to Veeam management services are restricted.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-26500 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-26500Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.