CVE-2025-30447
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 resolved by sanitizing logging. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. An app may be able to access sensitive user 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 · high confidenceThis vulnerability involved improper sanitization of sensitive user data in Apple system logs. An application could potentially access this sensitive information through the unsanitized log entries. The fix was implemented by sanitizing the logging mechanism across multiple Apple operating systems.
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< 17.7.6>= 18.0, < 18.4< 18.4>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4< 18.4< 2.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.
-
Identify your Apple device operating systemDetermine which Apple operating system is running on your device: iOS (iPhone), iPadOS (iPad), macOS (Mac computer), tvOS (Apple TV), or visionOS (Apple Vision Pro).Affected if The device runs any of the listed affected operating systems.
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About and note the Version number. Compare against affected ranges: iOS < 18.4 or iOS 17.x < 17.7.6; iPadOS < 18.4 or iPadOS 17.x < 17.7.6.Affected if The version is less than 18.4, or is 17.x and less than 17.7.6.
-
Check macOS versionOn Mac, go to System Settings > General > About (or System Preferences > About on older macOS) and note the Version number. Compare against affected ranges: macOS 13.x < 13.7.5, macOS 14.x < 14.7.5, or macOS 15.x < 15.4.Affected if The version is 13.x and less than 13.7.5, 14.x and less than 14.7.5, or 15.x and less than 15.4.
-
Check tvOS versionOn Apple TV, go to Settings > General > About and note the Version number. Compare against affected range: tvOS < 18.4.Affected if The version is less than 18.4.
-
Check visionOS versionOn Apple Vision Pro, go to Settings > General > About and note the Version number. Compare against affected range: visionOS < 2.4.Affected if The version is less than 2.4.
Your environment is affected if the installed operating system version matches any of the vulnerable version ranges listed for your Apple platform.
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 · scoped2.413.7.514.7.5
Update affected devices to the patched versions: iOS 18.4 or 17.7.6, iPadOS 18.4 or 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4.
iOS 18.4 / iPadOS 17.7.6 / iPadOS 18.4 / macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 / tvOS 18.4 / visionOS 2.4 / watchOS 11.4
- Identify the device type (iPhone, iPad, Mac, Apple TV, or Apple Vision Pro)
- Determine the current installed version from Settings > General > About (iOS/iPadOS) or System Settings/About This Mac (macOS)
- For iPhone: Upgrade to iOS 18.4
- For iPad: Upgrade to iPadOS 17.7.6 (if on iPadOS 17.x) or iPadOS 18.4 (if on iOS 18)
- For Mac: Upgrade to macOS Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4 depending on current macOS version
- For Apple TV: Upgrade to tvOS 18.4
- For Apple Vision Pro: Upgrade to visionOS 2.4
- For Apple Watch: Upgrade to watchOS 11.4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30447 — 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-30447 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