macOSOperating system · Apple

CVE-2023-32364

HIGH · 8.6 CVSS v3.1 Developing Published 2023-07-27
Fix available
A fix is available. Upgrade to 11.7.9 / 12.6.8 or later.
See remediation →
89/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
A logic issue was addressed with improved restrictions. This issue is fixed in macOS Ventura 13.5. A sandboxed process may be able to circumvent sandbox restrictions.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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:>= 11.0, < 11.7.9>= 12.0.0, < 12.6.8>= 13.0, < 13.5

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
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

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 11.7.9 / 12.6.8 / 13.5 or later
Fixed in 11.7.912.6.813.5
Recommended fix High confidence

macOS 11.7.9 (Big Sur), macOS 12.6.8 (Monterey), or macOS 13.5 (Ventura) - depending on which major version is currently installed

  1. Check current macOS version by clicking the Apple menu and selecting About This Mac
  2. Back up important data using Time Machine or another backup method
  3. Open System Settings (System Preferences on older macOS versions)
  4. Select General > Software Update
  5. Allow the system to check for updates
  6. If updates are available, click Update Now or Upgrade Now to install the security update
  7. For macOS 11.x (Big Sur), install macOS 11.7.9 or later; for macOS 12.x (Monterey), install macOS 12.6.8 or later; for macOS 13.x (Ventura), install macOS 13.5 or later
  8. Restart the computer when prompted to complete the update
Caveat Standard macOS security updates typically do not introduce breaking changes; however, some third-party applications may have compatibility issues with newer macOS versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32364 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32364 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