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-26500

HIGH · 8.8 CVSS v3.1 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 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
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.

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 · moderate confidence

Improper path limitation in Veeam Backup & Replication versions 9.5U3, 9.5U4, 10.x, and 11.x allows authenticated remote users to bypass restrictions on internal API functions, enabling arbitrary file upload and code execution.

MitigationApply vendor security patches for CVE-2022-26500 or upgrade to patched versions; restrict network exposure of Veeam services and monitor for suspicious API activity until remediation is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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= 9.5.0.1536= 9.5.4.2615= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Veeam Backup & Replication installation
    Check common installation paths such as C:\Program Files\Veeam\Backup and Replication\ or inspect the Windows Services panel for 'Veeam Backup Service'
    Affected if Veeam Backup & Replication is installed on the system
  2. Determine installed Veeam version
    Open Windows Services, right-click on 'Veeam Backup Service', select Properties, and note the 'File version' displayed, or run 'Get-VBRServer' via Veeam PowerShell if available
    Affected if The version falls within the affected ranges: 9.5.0.1536, 9.5.4.2615, any version from 10.0.0.4442 up to but not including 10.0.1.4854, or any version from 11.0.0.825 up to but not including 11.0.1.1261
  3. Verify Veeam API service is exposed
    Attempt to access https://localhost:9399/api/ or the configured Veeam API endpoint from the server itself, or check if port 9399/9443 is listening via 'netstat -an | findstr 9399'
    Affected if The Veeam API service (REST API) is running and accessible on the network
  4. Confirm API authentication is enabled
    Check if the Veeam Backup Service is running and if API access credentials are configured in Veeam; verify user accounts with API access exist in the Veeam console under 'Users and Roles'
    Affected if There are user accounts configured with API or console access permissions

You are affected if Veeam Backup & Replication is installed with a version matching the affected ranges AND the API service is running with at least one authenticated user account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Interim mitigation

Apply vendor security patches for CVE-2022-26500 or upgrade to patched versions; restrict network exposure of Veeam services and monitor for suspicious API activity until remediation is complete.

Recommended fix High confidence

10.0.1.4854 (for 10.x) or 11.0.1.1261 (for 11.x)

  1. Identify your current Veeam Backup & Replication version by checking the About section in the Veeam console or the installer
  2. If running version 10.0.0.4442 through 10.0.1.4853, download and install version 10.0.1.4854 or later from Veeam's download portal
  3. If running version 11.0.0.825 through 11.0.1.1260, download and install version 11.0.1.1261 or later from Veeam's download portal
  4. If running version 9.5.0.1536 or 9.5.4.2615, upgrade to a supported version (10.0.1.4854+ or 11.0.1.1261+) as version 9.5 is no longer supported
  5. Schedule maintenance window for upgrade as Veeam services will be briefly interrupted
  6. Ensure you have a valid backup of your Veeam configuration before upgrading
  7. Run the installer with administrative privileges and follow the upgrade wizard
  8. After upgrade, verify all services are running and test critical backup/restore operations
Caveat Upgrading may require service restart; ensure maintenance window is scheduled. Version 9.5 users must migrate to version 10 or 11 as 9.5 is end-of-life.

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

Fix this in Veeam Backup \& Replication Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26500 — 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-26500 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