LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26501: Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).

Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

This is a critical access-control flaw in Veeam Backup & Replication 10.x and 11.x. The public record rates it 9.8 because network attackers need no credentials or user interaction and could affect confidentiality, integrity, and availability. CISA lists it as known exploited, so exposed backup infrastructure should be treated as urgent.

Executive priority

Immediate priority. This affects backup infrastructure, has critical CVSS characteristics, and is listed by CISA as known exploited. Leadership should require rapid inventory, remediation tracking, and compensating network controls for any system not yet remediated.

Technical view

CVE-2022-26501 is mapped to CWE-306 and described as incorrect access control in Veeam Backup & Replication 10.x and 11.x. CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicates unauthenticated network reachability with high impact. The bundle does not provide protocol details, affected CPEs, or exploit mechanics.

Likely exposure

Likely exposure is organizations running Veeam Backup & Replication 10.x or 11.x, especially where Veeam services are reachable from untrusted networks. The provided CVE data lists affected CPEs as unavailable, so asset confirmation must come from internal inventory and vendor guidance.

Exploitation context

Active exploitation is supported by CISA KEV status for CVE-2022-26501. The source bundle does not include exploit details, observed campaigns, or indicators of compromise. Treat reachable instances as high priority because backup systems can affect recovery, ransomware resilience, and sensitive data access.

Researcher notes

The available bundle is sparse: it confirms product family, versions 10.x and 11.x, CWE-306, CVSS 9.8, Veeam KB4288, and CISA KEV status. It does not provide CPEs, fixed versions, exploit primitives, or detection indicators, so validation should avoid assumptions beyond vendor and CISA records.

Mitigation direction

  • Identify all Veeam Backup & Replication 10.x and 11.x deployments.
  • Review and follow Veeam KB4288 for authoritative remediation guidance.
  • Restrict Veeam service access to trusted administrative networks only.
  • Prioritize remediation for internet-facing or broadly reachable Veeam systems.
  • Monitor vendor and CISA guidance for updated instructions.

Validation and detection

  • Confirm product version for each Veeam Backup & Replication server.
  • Check whether each instance is covered by Veeam KB4288 remediation guidance.
  • Verify Veeam services are not exposed to untrusted networks.
  • Review security logs for unusual access to Veeam management services.
  • Document remediation status and exceptions for vulnerability management tracking.
Prepared
Reviewed
Confidence
medium
Sources
4

Michael Williams reviewed this cited source version on .

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-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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
cve · low confidence lookup

CVE-2022-26501 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
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-26501Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.