dbcve.org
macOSOperating system · Apple

CVE-2025-43414

MEDIUM · 6.2 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 14.8.2 / 15.7.2 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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
A permissions issue was addressed with improved validation. This issue is fixed in macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1. A shortcut may be able to access files that are normally inaccessible to the Shortcuts 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 · high confidence

A permissions bypass vulnerability in macOS Shortcuts allows shortcuts to access files that should be protected from the Shortcuts app due to insufficient validation of file access permissions.

MitigationUpdate to macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1 or later to apply the fix.

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:< 14.8.2>= 15.0, < 15.7.2

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

CVSS:3.1/AV:L/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 checks

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

  1. Check installed macOS version
    Open System Settings > General > About, or run 'sw_vers' in Terminal. Compare the version number against the affected ranges: < 14.8.2, or >= 15.0 and < 15.7.2
    Affected if The macOS version falls within the affected ranges (< 14.8.2 or >= 15.0 but < 15.7.2)
  2. Verify Shortcuts app permissions
    Open System Settings > Privacy & Security > Shortcuts. Review whether Shortcuts has been granted permission to access files or specific folders
    Affected if Shortcuts has file or folder access permissions granted
  3. Check for shortcuts accessing protected directories
    Open the Shortcuts app and review installed shortcuts. Look for any shortcuts that reference paths such as ~/Documents, ~/Desktop, or other user directories that should be protected
    Affected if Any shortcuts exist that access user files or directories that should require explicit permission
  4. Inspect Shortcuts app sandbox configuration
    Run 'codesign -d --entitlements - /System/Applications/Shortcuts.app/Contents/MacOS/Shortcuts' to view the app's sandbox entitlements, or check System Settings to see if Shortcuts has full disk access
    Affected if Shortcuts has Full Disk Access enabled or has entitlements allowing broad file system access

You are affected if your macOS version is below 14.8.2 or between 15.0 and 15.7.2, and the Shortcuts app has been granted file or folder access permissions that could bypass intended restrictions.

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 14.8.2 / 15.7.2 or later
Fixed in 14.8.215.7.2
Interim mitigation

Update to macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1 or later to apply the fix.

Recommended fix High confidence

macOS Sequoia 15.7.2 or macOS Sonoma 14.8.2 (or later)

  1. Back up your Mac using Time Machine or another backup method before updating
  2. Check your current macOS version by clicking the Apple menu > About This Mac
  3. If running macOS 15.0-15.7.1 (Sequoia), upgrade to macOS 15.7.2 or later by going to System Settings > General > Software Update
  4. If running macOS 14.0-14.8.1 (Sonoma), upgrade to macOS 14.8.2 or later by going to System Settings > General > Software Update
  5. If running macOS 13 or earlier, consider upgrading to a supported version (macOS 14.8.2 or later)
  6. After updating, verify the new version by checking About This Mac
Caveat Standard macOS update considerations apply - some legacy applications may have compatibility issues with newer macOS versions

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

Fix this in macOS Scoped from the published advisory
  • Consultation0.5 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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