CVE-2025-24236
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 · uneditedAn access issue was addressed with additional sandbox restrictions. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5. An app may be able to access sensitive user 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 confidenceThis is a sandbox bypass vulnerability in macOS where an application could potentially access sensitive user data due to insufficient sandbox restrictions. The issue was addressed by implementing additional sandbox controls in macOS Sequoia 15.4 and macOS Sonoma 14.7.5.
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.7.5>= 15.0, < 15.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 versionOpen System Settings > General > About, or run `sw_vers` in TerminalAffected if Version shows 14.0 to 14.7.4 (Sonoma) or 15.0 to 15.3 (Sequoia)
-
Confirm macOS build numberRun `system_profiler SPSoftwareDataType` in Terminal to see full version detailsAffected if Build number falls within affected range for your major version
-
Verify system is not running fixed versionsCompare your version to 14.7.5 (Sonoma) or 15.4 (Sequoia) - these are the patched releasesAffected if Installed version is below 14.7.5 (for 14.x) or below 15.4 (for 15.x)
You are affected if the system runs macOS Sonoma 14.0-14.7.4 or macOS Sequoia 15.0-15.3; the vulnerability is present in unpatched versions regardless of sandbox configuration, as it is a missing restriction in the OS itself.
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.515.4
Apply the macOS security updates (Sequoia 15.4 or Sonoma 14.7.5) to affected systems to enforce the corrected sandbox restrictions.
macOS Sonoma 14.7.5 or macOS Sequoia 15.4 depending on current OS version
- Back up important data before performing any system update
- If running macOS 14.x (Sonoma), upgrade to macOS 14.7.5
- If running macOS 15.x (Sequoia), upgrade to macOS 15.4
- After upgrade, verify the system is running the correct version by checking About This Mac
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24236 — 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-24236 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