CVE-2025-30443
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 privacy issue was addressed by removing the vulnerable code. This issue is fixed in macOS Sequoia 15.4, macOS Sequoia 15.5, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to access user-sensitive data.
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 macOS vulnerability allowed a malicious application to access user-sensitive data through a privacy bypass. The fix involved removing the vulnerable code from the affected macOS versions (Ventura 13.7.5, Sonoma 14.7.5, and Sequoia 15.4/15.5).
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>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 versionClick the Apple menu in the top-left corner of the screen, select 'About This Mac', and note the version number displayed under the macOS nameAffected if The version shown is 13.7.4 or earlier, 14.7.4 or earlier, or 15.3 or earlier (meaning it falls within any of the affected ranges: >=13.0,<13.7.5 or >=14.0,<14.7.5 or >=15.0,<15.4)
-
Confirm macOS release nameIn 'About This Mac', note the release name (Ventura, Sonoma, or Sequoia) to determine which version range applies to your systemAffected if You are running Ventura 13.7.4 or earlier, Sonoma 14.7.4 or earlier, or Sequoia 15.3 or earlier
-
Verify exact build version (optional)In 'About This Mac', click 'General' then 'System Report', and look at the 'Build Version' field under Software > macOSAffected if The build version corresponds to an unpatched release (contact Apple security announcements for specific build numbers if needed)
You are affected if your macOS version is 13.7.4 or earlier, 14.7.4 or earlier, or 15.3 or earlier, since these versions contain the vulnerable code that was removed in the patched 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 · scoped13.7.514.7.515.4
Update affected macOS devices to the specified patched versions (Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.5 or later) to remediate the vulnerability.
macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4/15.5 (depending on current major version)
- Identify the current macOS version by clicking the Apple menu and selecting 'About This Mac'
- If running macOS Ventura 13.x, upgrade to version 13.7.5 or later
- If running macOS Sonoma 14.x, upgrade to version 14.7.5 or later
- If running macOS Sequoia 15.0-15.3, upgrade to version 15.4 or later
- If running macOS Sequoia 15.4, upgrade to version 15.5 for additional security fixes
- Use System Settings > General > Software Update to install the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30443 — 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-30443 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