CVE-2025-31275
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 restrictions. This issue is fixed in macOS Sequoia 15.6. A sandboxed process may be able to launch any installed app.
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 sandboxed process in macOS Sequoia could bypass permission restrictions to launch any installed application, representing a privilege escalation vulnerability where an app running in a restricted sandbox could escape its containment to execute other programs on the system.
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< 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check macOS versionRun 'sw_vers -productVersion' in Terminal or open System Settings > About to view the macOS versionAffected if The version displayed is lower than 15.6 (e.g., 15.5, 15.4, 15.3, etc.)
-
Confirm macOS release nameRun 'sw_vers -productVersionExtra' or check the About window to confirm the system is macOS SequoiaAffected if The system is macOS Sequoia and the version is below 15.6
-
Identify sandboxed applicationsReview installed applications that operate within sandboxed environments - these are typically App Store applications or apps with sandbox entitlements visible in their code signing informationAffected if Sandboxed applications are installed on a system running macOS < 15.6, as the vulnerability allows such apps to escape their containment and launch other programs
You are affected if your macOS Sequoia system is running a version lower than 15.6 and has sandboxed applications installed that could potentially exploit this privilege escalation flaw.
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 · scoped15.6
Apply macOS Sequoia 15.6 or later to receive the additional permission restrictions that prevent sandboxed processes from launching arbitrary applications.
macOS Sequoia 15.6
- 1. Back up your Mac using Time Machine or another backup solution before performing any system update
- 2. Open System Settings (or System Preferences on older macOS versions)
- 3. Click on General in the sidebar
- 4. Click Software Update
- 5. Allow macOS to check for updates
- 6. If macOS Sequoia 15.6 is available, click Update Now or Download to install the update
- 7. Follow the on-screen prompts and restart your Mac when prompted to complete the installation
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-31275 — 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-31275 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