CVE-2025-24826
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 · uneditedLocal privilege escalation due to insecure folder permissions. The following products are affected: Acronis Snap Deploy (Windows) before build 4625.
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 confidenceLocal privilege escalation vulnerability in Acronis Snap Deploy for Windows. The vulnerability stems from insecure folder permissions that allow a local attacker to potentially gain elevated privileges on the system. Affected versions are prior to build 4625.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Acronis Snap Deploy is installedCheck the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Acronis Snap Deploy' or look in C:\Program Files\Acronis for a Snap Deploy folderAffected if No Acronis Snap Deploy installation is found, the system is not affected by this specific vulnerability
-
Locate the Acronis Snap Deploy installation directoryOpen File Explorer and navigate to C:\Program Files\Acronis\SnapDeploy or check the installation path from the registry Uninstall entryAffected if The installation directory does not exist or cannot be located
-
Check the installed build versionOpen Add or Remove Programs, find Acronis Snap Deploy, and note the version/build number displayed, or right-click the executable in the install folder and view Properties > DetailsAffected if The installed build number is less than 4625 (for example, 4600, 4500, or any build prior to 4625)
-
Examine folder permissions on the Snap Deploy installation directoryRight-click the Acronis Snap Deploy folder, select Properties, go to the Security tab, and review which users or groups have Full Control or Modify permissionsAffected if Users without administrator privileges have excessive permissions (Full Control or Modify) on the Snap Deploy installation folder, allowing potential privilege escalation
A system is affected if Acronis Snap Deploy is installed with a build number earlier than 4625 and the installation folder has overly permissive access controls that allow non-admin users to modify executable files or configuration.
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 · scopedUpgrade Acronis Snap Deploy to build 4625 or later to remediate the insecure folder permissions vulnerability.
Acronis Snap Deploy (Windows) build 4625 or later
- Download Acronis Snap Deploy (Windows) build 4625 or later from the official Acronis website or your licensed download portal
- Install the updated version of Acronis Snap Deploy on affected Windows systems
- Verify the installation completed successfully
- Confirm folder permissions have been corrected in the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24826 — 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-24826 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