CVE-2023-40436
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 · uneditedThe issue was addressed with improved bounds checks. This issue is fixed in macOS Sonoma 14. An attacker may be able to cause unexpected system termination or read kernel memory.
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 kernel-level vulnerability in macOS involving insufficient bounds checks allows an attacker to either cause a system crash (denial of service) or read kernel memory. This is a memory corruption issue that was patched in macOS Sonoma 14.
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.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
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 version via System SettingsOpen System Settings, then go to General > About. Note the version number displayed next to 'macOS'.Affected if The version shown is 13.x or earlier (any version number less than 14.0)
-
Check macOS version via command lineOpen Terminal and run: sw_vers -productVersionAffected if The output shows a version lower than 14.0 (for example, 13.5.2, 12.7.1, etc.)
-
Confirm the full version numberIn System Settings > About, also note the build number if displayed. Compare your version against the macOS Sonoma 14.0 release.Affected if Your macOS version is any build prior to macOS 14.0 (Sonoma)
A system is affected if it runs any version of macOS earlier than 14.0 (Sonoma), as the kernel vulnerability exists in all prior releases.
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.0
Apply macOS Sonoma 14 or later via standard Apple software update mechanisms. For enterprise environments, deploy via MDM/Apple School/Business Manager.
macOS Sonoma 14
- Back up your Mac using Time Machine or another backup method before performing the system update
- Verify your current macOS version by clicking the Apple menu and selecting About This Mac
- Open System Settings (or System Preferences on older macOS versions)
- Navigate to General > Software Update
- Allow the system to check for updates - if macOS Sonoma 14 is available, click Update Now or Download to begin the upgrade
- Follow the on-screen prompts to complete the installation, which may restart your Mac
- After the update completes, verify the new version by checking About This Mac to confirm macOS 14.x (Sonoma) is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40436 — 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-2023-40436 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