dbcve.org
macOSOperating system · Apple

CVE-2025-43330

HIGH · 8.2 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 15.7 or later.
See remediation →
85/100
Remediation priority · High
No privileges

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
This issue was addressed by removing the vulnerable code. This issue is fixed in macOS Sequoia 15.7, macOS Tahoe 26. An app may be able to break out of its sandbox.

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 confidence

Sandbox escape vulnerability in macOS where an application could potentially break out of its sandbox isolation and execute code outside its intended security boundary. The vulnerability was addressed by removing the vulnerable code path.

MitigationApply the macOS security updates (Sequoia 15.7 or Tahoe 26 or later) to remediate this vulnerability. Organizations should verify all managed macOS devices have received the update.

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
macOSOperating system
Affected:< 15.7

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 checks

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

  1. Check macOS version via Terminal
    Run the command: sw_vers -productVersion
    Affected if The version displayed is less than 15.7 (e.g., 15.6, 15.5, 14.x, etc.)
  2. Check macOS version via System Information
    Open System Information (or System Profiler) and look at the macOS version listed under Software > System Software Overview
    Affected if The installed macOS version is earlier than 15.7
  3. Check system update status
    Run: softwareupdate --list or go to System Settings > General > Software Update to see available updates
    Affected if Updates to version 15.7 or later are available but not yet installed

Your macOS environment is affected if the installed version is below 15.7, as the sandbox escape vulnerability exists in versions prior to this update.

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
Upgrade available Upgrade to 15.7 or later
Fixed in 15.7
Interim mitigation

Apply the macOS security updates (Sequoia 15.7 or Tahoe 26 or later) to remediate this vulnerability. Organizations should verify all managed macOS devices have received the update.

Recommended fix High confidence

macOS Sequoia 15.7 or later

  1. Back up your Mac using Time Machine or another backup solution before updating
  2. Open System Settings (or System Preferences on older macOS versions)
  3. Navigate to General > Software Update
  4. Wait for macOS to check for updates
  5. If macOS Sequoia 15.7 or later is available, click Download and Install
  6. Follow the on-screen prompts to complete the installation
  7. Restart your Mac when prompted to complete the update

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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