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 12 Sep 2023. Known ransomware use
Veeam Backup \& ReplicationApplication · Veeam

CVE-2023-27532

HIGH · 7.5 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to 11.0.1.1261 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS 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
Vulnerability in Veeam Backup & Replication component allows encrypted credentials stored in the configuration database to be obtained. This may lead to gaining access to the backup infrastructure hosts.

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

Veeam Backup & Replication contains a vulnerability allowing unauthorized retrieval of encrypted credentials from its configuration database. Attackers who obtain these credentials can potentially decrypt them and use them to access backup infrastructure hosts.

MitigationApply the vendor-provided patch for CVE-2023-27532 to Veeam Backup & Replication. Review and rotate credentials for backup infrastructure hosts as a precautionary measure.

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:< 11.0.1.1261= 11.0.1.1261= 12.0.0.1420

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
None
Availability
None

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

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. Determine Veeam Backup & Replication version
    Open Windows Registry and navigate to HKLM\SOFTWARE\Veeam\Veeam Backup & Replication\, or run 'Get-VBRBackupInfrastructure' in Veeam PowerShell, or check the Veeam Enterprise Manager web UI footer for the version number
    Affected if The installed version is 12.0.0.1420, 11.0.1.1261, or any version lower than 11.0.1.1261 in the 11.x line
  2. Verify configuration database exists
    Locate the Veeam configuration database (typically a .mdx or .sqlite file in the Veeam Data folder, default path: C:\ProgramData\Veeam\Backup\ or check registry key HKLM\SOFTWARE\Veeam\Veeam Backup & Replication\ConfigDb for the connection string)
    Affected if The configuration database file exists (it stores all encrypted credentials by design in vulnerable versions)
  3. Confirm credential storage is in use
    Open Veeam Backup & Replication Console, go to Menu > Credentials and Passwords, or run 'Get-VBRCredentials' in Veeam PowerShell to list stored credentials
    Affected if Any backup infrastructure credentials are stored in the Veeam configuration (this is the data targeted by the vulnerability)

You are affected if your Veeam Backup & Replication version is 12.0.0.1420, 11.0.1.1261, or any version earlier than 11.0.1.1261, AND you have credentials stored in the Veeam configuration database.

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 11.0.1.1261 or later
Fixed in 11.0.1.1261
Interim mitigation

Apply the vendor-provided patch for CVE-2023-27532 to Veeam Backup & Replication. Review and rotate credentials for backup infrastructure hosts as a precautionary measure.

Recommended fix High confidence

Veeam Backup & Replication 11.0.1.1262+ or 12.0.0.1421+ (latest 12.x recommended)

  1. 1. Identify current Veeam Backup & Replication version via Help > About in the console or via PowerShell: Get-VBRServerInfo
  2. 2. If running version 11.0.1.1261 or earlier, upgrade to version 11.0.1.1262 or later
  3. 3. If running version 12.0.0.1420, upgrade to version 12.0.0.1421 or later
  4. 4. Alternatively, upgrade to the latest available version of Veeam Backup & Replication (12.x recommended for latest features and security)
  5. 5. After upgrade, verify the installation was successful and test backup operations
  6. 6. Review and rotate any credentials that may have been compromised via this vulnerability
Caveat Major version upgrades (11.x to 12.x) may require license update and compatibility review; test in non-production first

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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