CVE-2025-43332
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 file quarantine bypass was addressed with additional checks. This issue is fixed in macOS Sequoia 15.7, macOS Sonoma 14.8, 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 · high confidenceCVE-2025-43332 is a macOS vulnerability where a file quarantine bypass allows an application to escape its sandbox. The file quarantine mechanism in macOS marks downloaded files with metadata to enforce security restrictions; the bypass involves circumventing these checks. This was fixed in macOS Sequoia 15.7, macOS Sonoma 14.8, and macOS Tahoe 26 with additional validation checks.
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>= 15.0, < 15.7CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 -productVersion' in Terminal or select Apple menu > About This MacAffected if Version is 14.0 to 14.7.x or 15.0 to 15.6.x (vulnerable range)
-
Confirm macOS familyRun 'sw_vers -productVersion' and note the major version number (14 = Sonoma, 15 = Sequoia)Affected if Running Sonoma 14.x or Sequoia 15.x before the fixed releases
-
Verify file quarantine is enabledRun 'defaults read com.apple.LaunchServices' or check System Settings > Privacy & Security for 'Quarantine' entries; also check /var/vm/swapfile permissions if quarantine metadata is being applied to downloadsAffected if File quarantine is turned ON (the bypass only applies when quarantine enforcement is active)
You are affected if your macOS version is 14.0-14.7.x or 15.0-15.6.x AND file quarantine is enabled in your system settings.
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.815.7
Apply the appropriate macOS security update (Sequoia 15.7, Sonoma 14.8, or Tahoe 26) to affected systems. Ensure file quarantine remains enabled in System Settings > Privacy & Security.
macOS Sonoma 14.8+ or macOS Sequoia 15.7+
- Check current macOS version by clicking the Apple menu > About This Mac
- If running macOS 14.0-14.7 (Sonoma), upgrade to macOS 14.8 or later via System Settings > General > Software Update
- If running macOS 15.0-15.6 (Sequoia), upgrade to macOS 15.7 or later via System Settings > General > Software Update
- Ensure the upgrade completes successfully and restart if prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43332 — 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-43332 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