dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jan 2023. Known ransomware use
Veeam Backup \& ReplicationApplication · Veeam

CVE-2022-26501

CRITICAL · 9.8 CVSS v3.1 Developing Published 2022-03-17
Fix available
A fix is available. Upgrade to 10.0.1.4854 / 11.0.1.1261 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-22.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Veeam Backup \& ReplicationApplication
Affected:>= 10.0.0.4442, < 10.0.1.4854>= 11.0.0.825, < 11.0.1.1261= 10.0.1.4854= 11.0.1.1261

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.1.4854 / 11.0.1.1261 or later
Fixed in 10.0.1.485411.0.1.1261
Recommended fix High confidence

Veeam Backup & Replication 10.0.1.4855+ or 11.0.1.1262+ (latest respective release)

  1. 1. Identify the current installed version of Veeam Backup & Replication from the console or installer
  2. 2. If running version 10.0.0.4442 through 10.0.1.4854, plan upgrade to version 10.0.1.4855 or later
  3. 3. If running version 11.0.0.825 through 11.0.1.1261, plan upgrade to version 11.0.1.1262 or later
  4. 4. Review Veeam upgrade documentation and release notes for prerequisites
  5. 5. Ensure backups are verified and a snapshot/image-level backup of the Veeam server exists
  6. 6. Schedule maintenance window for the upgrade process
  7. 7. Download the updated installer from Veeam's official download portal
  8. 8. Run the installer and follow the upgrade wizard prompts
Caveat Standard upgrade; review release notes for any configuration changes or known issues before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data