dbcve.org
Veeam Agent For WindowsApplication · Veeam

CVE-2025-48982

HIGH · 7.8 CVSS v3.1 Published 2025-10-31
Fix available
A fix is available. Upgrade to 6.3.2.1302 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
This vulnerability in Veeam Agent for Microsoft Windows allows for Local Privilege Escalation if a system administrator is tricked into restoring a malicious file.

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 Agent for Microsoft Windows contains a local privilege escalation vulnerability where the file restoration process does not properly validate or sanitize files being restored. If a system administrator is tricked into restoring a malicious file, an attacker can gain elevated (likely SYSTEM) privileges on the affected system.

MitigationAdministrators should only restore backup files from trusted, verified sources and should verify backup integrity before restoration. Organizations should implement strict change control processes for backup restoration activities.

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 Agent For WindowsApplication
Affected:>= 6.0.0.959, < 6.3.2.1302

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Verify Veeam Agent for Windows is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Veeam*"}' in PowerShell
    Affected if Veeam Agent for Windows appears in the installed programs list
  2. Determine the installed version
    Run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Veeam Agent*"}' and note the Version field, or check the About section in the Veeam Agent GUI
    Affected if The version number is >= 6.0.0.959 and < 6.3.2.1302
  3. Confirm file restore capability is available
    Launch Veeam Agent for Windows and navigate to the restore or backup section in the GUI, or check if the Veeam Agent service is running and has restore functionality enabled
    Affected if File restoration feature is present and enabled on the system
  4. Identify the Veeam Agent service privileges
    Open Services (services.msc), locate the Veeam Agent for Windows service, right-click and select Properties, then check the 'Log on as' account
    Affected if The service runs under SYSTEM or an elevated local system account (which is the default configuration)

A system is affected if Veeam Agent for Windows version 6.0.0.959 through 6.3.2.1301 is installed AND the file restoration feature is available or has been used, since the vulnerability exploits the restore process to gain SYSTEM privileges.

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

Administrators should only restore backup files from trusted, verified sources and should verify backup integrity before restoration. Organizations should implement strict change control processes for backup restoration activities.

Recommended fix High confidence

Veeam Agent for Windows 6.3.2.1302 or later

  1. Verify current Veeam Agent for Windows version by opening the Veeam Agent control panel or checking Add/Remove Programs
  2. Download Veeam Agent for Windows version 6.3.2.1302 or later from the official Veeam download page (www.veeam.com)
  3. Ensure you have a valid backup of your system before proceeding with any upgrade
  4. Run the Veeam Agent for Windows installer with administrative privileges
  5. Follow the on-screen upgrade wizard prompts to complete the installation
  6. After upgrade, verify the new version by checking Help > About in the Veeam Agent interface
  7. Confirm the vulnerability is resolved by ensuring the installed version is 6.3.2.1302 or higher
Caveat Review Veeam release notes for version 6.3.2 for any configuration or feature changes before upgrading; test in non-production environment first

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

Fix this in Veeam Agent For Windows Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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