CVE-2025-43192
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 configuration issue was addressed with additional restrictions. This issue is fixed in macOS Sequoia 15.6, macOS Sonoma 14.7.7. Account-driven User Enrollment may still be possible with Lockdown Mode turned on.
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 confidenceA configuration issue in macOS allowed Account-driven User Enrollment (an MDM feature) to function even when Lockdown Mode was enabled, effectively bypassing the intended security restriction. This was fixed in macOS Sequoia 15.6 and macOS Sonoma 14.7.7 with additional restrictions.
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< 14.7.7>= 15.0, < 15.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Check installed macOS versionRun 'sw_vers -productVersion' in Terminal or open System Settings > General > About to view the version numberAffected if Version is less than 14.7.7 OR between 15.0 and 15.5 (inclusive)
-
Verify MDM Account-driven User Enrollment is configuredCheck System Settings > General > About > Device Management, or run 'profiles status' in Terminal to see if an MDM profile with user enrollment is installedAffected if An MDM profile with Account-driven User Enrollment is present on the system
-
Check if Lockdown Mode is enabledOpen System Settings > Privacy & Security and look for the Lockdown Mode toggle, or use 'nvram -p' to check boot-args for 'lockdown-mode' settingAffected if Lockdown Mode is currently turned ON
-
Confirm enrollment still works with Lockdown ModeWith Lockdown Mode enabled, attempt to access MDM-enrolled services or check if user authentication to the MDM identity still succeeds (such as logging in with the enrolled managed Apple ID)Affected if User can successfully authenticate to MDM services despite Lockdown Mode being enabled - this indicates the bypass is present
You are affected if your macOS version is below 14.7.7 or between 15.0-15.5, you have MDM Account-driven User Enrollment configured, and user authentication to MDM succeeds even when Lockdown Mode is enabled.
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 · scoped14.7.715.6
Apply the appropriate macOS security update (15.6 for Sequoia, 14.7.7 for Sonoma) and verify that Lockdown Mode now properly restricts Account-driven User Enrollment in MDM configurations.
macOS Sonoma 14.7.7 or macOS Sequoia 15.6
- Check current macOS version by clicking the Apple menu > About This Mac
- Back up critical data using Time Machine or another backup solution before proceeding with the OS upgrade
- Upgrade to macOS Sonoma 14.7.7 if running a version earlier than 14.7.7
- Upgrade to macOS Sequoia 15.6 if running macOS 15.0 through 15.5
- To perform the upgrade, go to System Settings > General > Software Update and install the available update
- Restart the device when prompted to complete the installation
- Verify the upgrade was successful by checking About This Mac shows the correct version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43192 — 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-43192 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