CVE-2025-43373
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 memory handling. This issue is fixed in macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1. An app may be able to cause unexpected system termination or corrupt 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 confidenceThis is a memory handling vulnerability in macOS kernel that allows a malicious application to corrupt kernel memory or cause a system crash (kernel panic). The vulnerability likely involves improper memory allocation, deallocation, or access in a privileged kernel component, allowing a user-space application to manipulate kernel memory with potentially serious security implications.
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.8.2>= 15.0, < 15.7.2CVSS 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
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed macOS versionOpen Terminal and run: sw_vers -productVersionAffected if The version displayed is 14.0 through 14.8.1, or 15.0 through 15.7.1 (versions before the fixes in 14.8.2 and 15.7.2)
-
Confirm macOS name and buildRun: sw_vers in Terminal to see both product name (Sonoma, Sequoia, etc.) and build numberAffected if The build number is earlier than the fixed releases for your macOS version
Your system is affected if it runs macOS Sonoma 14.0-14.8.1 or macOS Sequoia 15.0-15.7.1, as these versions contain the vulnerable kernel memory handling code.
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.8.215.7.2
Apply the appropriate macOS security update: macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, or macOS Tahoe 26.1. This is a critical kernel-level fix that should be prioritized given the CVSS 7.5 severity and potential for system compromise.
macOS Sonoma 14.8.2, macOS Sequoia 15.7.2, or macOS Tahoe 26.1 (depending on current major version)
- Check current macOS version by going to System Settings > General > About
- Backup important data before performing system updates
- For macOS 14.x (Sonoma): Go to System Settings > General > Software Update and install macOS Sonoma 14.8.2
- For macOS 15.x (Sequoia): Go to System Settings > General > Software Update and install macOS Sequoia 15.7.2
- For macOS 26.x (Tahoe): Go to System Settings > General > Software Update and install macOS Tahoe 26.1
- Restart the system when prompted to complete the update
- Verify the update was successful by checking System Settings > General > About shows the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43373 — 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-43373 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