CVE-2026-28727
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 Unix socket permissions. The following products are affected: Acronis Cyber Protect 17 (macOS) before build 41186, Acronis Cyber Protect Cloud Agent (macOS) before build 41124, Acronis True Image (macOS) before build 42902.
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 macOS products due to insecure Unix socket permissions. An unprivileged local user could exploit improperly configured Unix socket access controls to gain elevated privileges on the affected system.
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< c25.10< 17.0.41186CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Identify installed Acronis product and versionOpen Terminal and run: ls /Applications | grep -i acronis to find installed Acronis applications, then check version via: ls /Applications/Acronis\*/Contents/Info.plist 2>/dev/null | xargs -I {} plutil -p {} | grep -i versionAffected if Version is earlier than c25.10 for Acronis Agent or earlier than 17.0.41186 for Acronis Cyber Protect
-
Verify Acronis service is runningRun: ps aux | grep -i acronis | grep -v grep to check if any Acronis daemon processes are activeAffected if Acronis agent/service processes are running on a version prior to the fixed builds
-
Check for Unix socket files created by AcronisRun: find /var /tmp /Library/Application\ Support/Acronis -name "*.sock" -type s 2>/dev/null to locate any Unix domain sockets created by Acronis componentsAffected if Unix sockets exist and are owned by root with overly permissive permissions (e.g., 777 or 666)
-
Inspect socket file permissionsFor each socket file found, run: ls -la <socket_path> to examine owner, group, and permission bitsAffected if Socket is world-writable or group-writable by a non-privileged group, allowing unprivileged users to communicate with the privileged service
User is affected if running Acronis Agent before c25.10 or Acronis Cyber Protect before 17.0.41186, with the Acronis service running and Unix sockets present with weak access controls.
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 · scoped17.0.41186
Upgrade Acronis Cyber Protect 17 to build 41186 or later, Acronis Cyber Protect Cloud Agent to build 41124 or later, and Acronis True Image to build 42902 or later.
Acronis Cyber Protect 17: build 41186+ | Cyber Protect Cloud Agent: build 41124+ | True Image: build 42902+ | Agent: c25.10+
- Identify the installed Acronis product (Cyber Protect 17, Cyber Protect Cloud Agent, or True Image) on macOS systems
- Determine the current build version of the installed Acronis software
- For Acronis Cyber Protect 17 (macOS): Upgrade to build 41186 or later
- For Acronis Cyber Protect Cloud Agent (macOS): Upgrade to build 41124 or later
- For Acronis True Image (macOS): Upgrade to build 42902 or later
- Verify the upgrade was successful by checking the updated build number
- Confirm the Unix socket permissions have been corrected in the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28727 — 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-2026-28727 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