CVE-2025-30445
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 type confusion issue was addressed with improved checks. 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. An attacker on the local network may cause an unexpected app termination.
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 confidenceA type confusion vulnerability in Apple's networking stack allows an authenticated attacker on the local network to trigger improper type handling, leading to unexpected app termination (denial of service). This is a memory safety issue where the software fails to validate object types before operations.
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.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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 iOS/iPadOS versionGo to Settings > General > About and note the software version (e.g., 18.3.1). For iPadOS, the affected versions are < 17.7.6 OR >= 18.0 and < 18.4. For iOS (iPhone), affected versions are < 18.4.Affected if The version falls outside the fixed releases (iPadOS 17.7.6+, 18.4+; iOS 18.4+)
-
Check macOS versionGo to System Settings > About (or Apple menu > About This Mac) and note the version (e.g., 15.3.1). Affected macOS versions: < 13.7.5 OR >= 14.0 and < 14.7.5 OR >= 15.0 and < 15.4.Affected if The version falls outside the fixed releases (13.7.5+, 14.7.5+, 15.4+)
-
Check tvOS or visionOS versionFor tvOS: go to Settings > General > About > Version. For visionOS: go to Settings > About. Affected: tvOS < 18.4, visionOS < 2.4.Affected if The version is below the fixed releases (tvOS 18.4+, visionOS 2.4+)
-
Verify network accessibilityConfirm the device has an active network connection (Wi-Fi or Ethernet). This vulnerability is exploitable by an authenticated attacker on the local network.Affected if The device is connected to a network where untrusted devices could access it
The device is affected if it runs any iOS < 18.4, iPadOS < 17.7.6 or 18.0-18.3.x, macOS < 13.7.5/14.7.5/15.4, tvOS < 18.4, or visionOS < 2.4 AND is accessible on a local network where untrusted attackers could reach it.
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
Apply the vendor-supplied patches (iOS 18.4/iPadOS 17.7.6+, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5+, tvOS 18.4, visionOS 2.4) to all affected devices. Until patched, restrict local network access to trusted devices only.
iPadOS: 17.7.6 or 18.4 (depending on device capability) | iPhone OS: 18.4 | macOS Ventura: 13.7.5 | macOS Sonoma: 14.7.5 | macOS Sequoia: 15.4 | tvOS: 18.4 | visionOS: 2.4
- Determine the current version of the affected device (iPad, iPhone, Mac, Apple TV, or Apple Vision Pro) by going to Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30445 — 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-30445 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