LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21668: A vulnerability allowing an authenticated domain user to bypass restrictions and manipulate arbitrary files...

A vulnerability allowing an authenticated domain user to bypass restrictions and manipulate arbitrary files on a Backup Repository.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Veeam Backup and Replication flaw could let a logged-in domain user bypass controls and manipulate files on a backup repository. Because repositories hold recovery data, compromise can threaten backup integrity, confidentiality, and availability.

Executive priority

Treat as high priority because backup repositories are critical to recovery. Remediate exposed Veeam 12.3.2 deployments promptly, especially where domain compromise would endanger backups needed for ransomware recovery.

Technical view

CVE-2026-21668 affects Veeam Backup and Replication 12.3.2. The record describes a restriction bypass by an authenticated domain user enabling arbitrary file manipulation on a Backup Repository. CVSS 3.1 is 8.8: network reachable, low complexity, low privileges, no user interaction, high CIA impact.

Likely exposure

Organizations running Veeam Backup and Replication 12.3.2 are the stated exposure group. Risk is highest where ordinary domain accounts can reach Veeam services or backup repository paths, or where repository access is not tightly isolated.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The attack requires an authenticated domain user, so compromised domain credentials or malicious insiders are the main practical concern.

Researcher notes

Evidence is limited to the CVE record and Veeam advisory reference. Do not assume unauthenticated exploitation, public exploit availability, or a specific fixed build unless confirmed in Veeam KB4830 or later vendor material.

Mitigation direction

  • Review Veeam KB4830 for official fixed versions and guidance.
  • Prioritize remediation for internet-adjacent or broadly reachable Veeam environments.
  • Restrict domain user access to Veeam infrastructure and repositories.
  • Harden repository ACLs and administrative group membership.
  • Monitor repositories for unexpected file changes or deletions.

Validation and detection

  • Inventory Veeam Backup and Replication instances and confirm versions.
  • Identify any systems running version 12.3.2.
  • Review repository permissions for excessive domain user access.
  • Check Veeam and storage logs for unusual repository file activity.
  • Confirm remediation status against Veeam KB4830.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2026-21668 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
No
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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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.9hackerone

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-21668Attack 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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VeeamBackup and Replication12.3.2unaffected
Weakness

CWE details

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

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.