dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-7779

HIGH · 8.8 CVSS v3.0 Published 2025-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Local privilege escalation due to insecure XPC service configuration. The following products are affected: Acronis True Image (macOS) before build 42389, Acronis True Image for SanDisk (macOS) before build 42198, Acronis True Image for Western Digital (macOS) before build 42197, Acronis True Image OEM (macOS) before build 42571.

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

Acronis True Image for macOS ships with an XPC service that is configured with insecure permissions or entitlements, allowing a local attacker to interact with the service and escalate privileges to root by exploiting the inter-process communication mechanism.

MitigationUpdate Acronis True Image (or the appropriate OEM variant) to the fixed build number (42389 for standard, 42198 for SanDisk, 42197 for Western Digital, 42571 for OEM).

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

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

  1. Verify Acronis True Image is installed
    Check if Acronis True Image.app exists in /Applications/ or scan for Acronis components in /Library/Application Support/Acronis/ using ls
    Affected if The application or its components are present on the system
  2. Identify the installed variant
    Check the application name in /Applications/ (e.g., Acronis True Image, SanDisk SSD Toolkit, WD Discovery) or inspect the bundle identifier with: defaults read /Applications/Acronis\ True\ Image.app/Contents/Info CFBundleIdentifier
    Affected if Any Acronis True Image variant is installed, as all variants share the vulnerable XPC service code
  3. Check the installed build number
    Run: defaults read /Applications/Acronis\ True\ Image.app/Contents/Info CFBundleVersion or right-click the app in Finder > Get Info to view the Version field which shows the build number
    Affected if The build number is below 42389 for standard version, below 42198 for SanDisk variant, below 42197 for WD variant, or below 42571 for OEM variant
  4. Confirm the XPC service is present
    List the contents of /Library/Application Support/Acronis/ to locate the XPC service bundle (look for com.acronis.*.xpc entries), then inspect its Info.plist for the ServiceType key
    Affected if An XPC service from Acronis exists on the system, indicating the vulnerable service component is deployed

If Acronis True Image (any variant) is installed with a build number lower than the fixed threshold for that variant, the system is vulnerable to local privilege escalation via the insecure XPC service.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Acronis True Image (or the appropriate OEM variant) to the fixed build number (42389 for standard, 42198 for SanDisk, 42197 for Western Digital, 42571 for OEM).

Recommended fix High confidence

Acronis True Image (macOS) build 42389 or later; Acronis True Image for SanDisk (macOS) build 42198 or later; Acronis True Image for Western Digital (macOS) build 42197 or later; Acronis True Image OEM (macOS) build 42571 or later

  1. 1. Open Acronis True Image on the affected macOS system
  2. 2. Navigate to the application menu (Acronis True Image > Check for Updates) or use Help > Check for Updates
  3. 3. If an update is available, download and install the latest version
  4. 4. Alternatively, download the latest installer from the official Acronis website or your OEM partner (SanDisk, Western Digital)
  5. 5. Uninstall the current version if the auto-update does not reach the fixed build
  6. 6. Install the updated version with the fixed build number
  7. 7. Restart the system to ensure the XPC service is properly reconfigured
  8. 8. Verify the installed build number matches or exceeds the fixed version (Acronis True Image: 42389+, SanDisk: 42198+, Western Digital: 42197+, OEM: 42571+)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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