CVE-2025-48983
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 · uneditedA vulnerability in the Mount service of Veeam Backup & Replication, which allows for remote code execution (RCE) on the Backup infrastructure hosts by an authenticated domain user.
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 confidenceA vulnerability in the Mount service of Veeam Backup & Replication allows an authenticated domain user to execute arbitrary code remotely on Backup infrastructure hosts, potentially compromising the entire backup infrastructure.
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>= 12.0.0.1402, < 12.3.2.4165CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Veeam Backup & Replication versionOpen Veeam Backup & Replication console, go to Help > About, or run 'Get-VBRVersion' PowerShell command on the backup server to retrieve the exact version numberAffected if Installed version falls within 12.0.0.1402 to 12.3.2.4165 (inclusive of start, exclusive of fix)
-
Verify Mount service is enabledIn Veeam console, navigate to Backup Infrastructure > Backup Repositories, or check Windows Services on the backup server for 'Veeam Mount Service' statusAffected if Mount service is installed and running, exposing the vulnerable component
-
Check Mount service network exposureReview firewall rules on the backup server to determine if TCP port 2500 (default Mount service port) is open to network access beyond localhostAffected if Mount service port is accessible from network segments containing non-admin domain users
-
Audit domain user permissions to Mount serviceIn Veeam console, go to Users and Roles > Role Assignment, or check AD group membership for users with Backup Operator or equivalent domain-level permissionsAffected if Non-administrative domain user accounts or groups have permissions that allow Mount service access
Environment is affected if Veeam Backup & Replication version is between 12.0.0.1402 and 12.3.2.4165, the Mount service is enabled, and non-admin domain users have access to it.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.3.2.4165
Apply vendor-provided security patches for CVE-2025-48983 immediately; until patch is available, restrict network access to the Mount service and limit domain user privileges to least-privilege principles.
Veeam Backup & Replication 12.3.2.4165 or later
- Verify current Veeam Backup & Replication version by opening the Veeam Backup & Replication console and checking About section, or via PowerShell with Get-VBRServerInfo
- Download Veeam Backup & Replication version 12.3.2.4165 or later from the official Veeam downloads page (www.veeam.com)
- Create a full backup of the Veeam configuration using the Veeam Backup & Replication console (Backup Infrastructure > Jobs > Configuration Backup)
- Schedule any active backup jobs to pause during the upgrade window
- Stop all Veeam services on the backup server (or use the Veeam Installer Service)
- Run the Veeam Backup & Replication installer with Administrator privileges
- Follow the on-screen upgrade wizard, selecting the upgrade option
- Restart the server if prompted by the installer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48983 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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