CVE-2025-10906
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 flaw has been found in Magnetism Studios Endurance up to 3.3.0 on macOS. This affects the function loadModuleNamed:WithReply of the file /Applications/Endurance.app/Contents/Library/LaunchServices/com.MagnetismStudios.endurance.helper of the component NSXPC Interface. Executing manipulation can lead to missing authentication. The attack needs to be launched locally. The exploit has been published and may be used.
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 confidenceThe Endurance app's XPC helper service (com.MagnetismStudios.endurance.helper) lacks authentication verification in the loadModuleNamed:WithReply function, allowing local unprivileged users to potentially load arbitrary modules into the application without proper authorization.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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.
-
Find installed Endurance application versionLocate the Endurance app in /Applications or ~/Applications, right-click and select 'Get Info', or run: defaults read /Applications/Endurance.app/Contents/Info.plist CFBundleShortVersionStringAffected if Version is 3.3.0 or lower (the fix is planned for versions beyond 3.3.0)
-
Identify the helper tool installationCheck for the presence of the helper tool using: ls -la /Library/PrivilegedHelperTools/ | grep -i endurance or ls -la ~/Library/Application\ Support/Endurance/Affected if The helper tool com.MagnetismStudios.endurance.helper is installed on the system
-
Verify helper tool file permissionsRun: ls -l /Library/PrivilegedHelperTools/com.MagnetismStudios.endurance.helper to check owner and permissionsAffected if Helper is owned by root and has setuid bit, or permissions allow unauthorized access
-
Confirm helper is running as a privileged XPC serviceCheck running processes for the helper: ps aux | grep -i 'endurance.helper' or examine LaunchDaemon configuration in /Library/LaunchDaemons/Affected if The helper daemon is loaded and running with elevated (root) privileges
-
Test for unauthenticated XPC access (if safe to do so)Examine the helper's XPC interface code if accessible, or review system logs for XPC connection attempts from non-root usersAffected if XPC service accepts connections without code signing or authentication validation
User is affected if Endurance version is 3.3.0 or lower AND the com.MagnetismStudios.endurance.helper tool is installed with elevated privileges, since the XPC interface accepts unauthenticated module loading requests.
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.
From vendor dataApply vendor patch when available; until then, restrict local user access to the system and monitor for suspicious use of the XPC helper service.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10906 — 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-10906 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