CVE-2025-43405
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 permissions issue was addressed with additional sandbox restrictions. This issue is fixed in macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1. An app may be able to access user-sensitive data.
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 permissions bypass in macOS sandboxing allowed an application to access user-sensitive data that should have been protected by sandbox restrictions. The vulnerability was addressed with additional sandbox enforcement controls in the specified macOS versions.
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.0, < 14.8.2>= 15.0, < 15.7.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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' in Terminal or go to System Settings > General > About to view the macOS version (e.g., 14.7.1, 15.6.2)Affected if Version is 14.0 to 14.8.1 (Sonoma) or 15.0 to 15.7.1 (Sequoia)
-
Confirm exact build numberRun 'uname -a' or check System Settings > General > About > Version for the build number (e.g., 23G93)Affected if Build number falls within affected ranges for the detected major version
-
Verify sandbox is enabledRun 'sandboxctl list --active' or check if sandboxing is enforced for applications via system logsAffected if Sandbox is enabled and the OS version is within the vulnerable range (the bypass only affects sandboxed apps)
-
Check for security updates installedRun 'system_profiler SPSoftwareDataType' to view installed updates, or check System Settings > General > Software Update for recent security patchesAffected if No security update addressing CVE-2025-43405 has been installed on a vulnerable macOS version
A user is affected if their macOS version is 14.0-14.8.1 or 15.0-15.7.1 AND sandbox is enabled, since the vulnerability allows sandboxed applications to bypass restrictions and access protected user data.
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.8.215.7.2
Update macOS to version Sequoia 15.7.2, Sonoma 14.8.2, or Tahoe 26.1 or later to apply the sandbox restrictions that prevent unauthorized access to sensitive user data.
macOS Sonoma 14.8.2 or macOS Sequoia 15.7.2 depending on current major version
- Identify current macOS version by clicking Apple menu > About This Mac
- For macOS 14.x (Sonoma): Navigate to System Settings > General > Software Update and install macOS Sonoma 14.8.2
- For macOS 15.x (Sequoia): Navigate to System Settings > General > Software Update and install macOS Sequoia 15.7.2
- Restart the system when prompted to complete the update
- Verify the update was successful by checking About This Mac shows the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43405 — 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-43405 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