CVE-2025-24129
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.3 and iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3. 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 · moderate confidenceA type confusion vulnerability in Apple's ecosystem (iOS, iPadOS, macOS, tvOS, visionOS) allows an attacker on the local network to trigger unexpected app termination via malformed network interactions. The vulnerability stems from insufficient type validation during network request processing, leading to a denial-of-service condition.
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< 18.3< 18.3< 15.3< 18.3< 2.3< 11.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 version on iPhone/iPadGo to Settings > General > About > Version, or run 'sw_vers' via Terminal, or check via Apple Configurator, MDM, or device management consoleAffected if Version is earlier than 18.3 and the device connects to networks with untrusted devices
-
Check iPadOS versionGo to Settings > General > About > Version, or run 'sw_vers' via Terminal, or check via Apple Configurator, MDM, or device management consoleAffected if Version is earlier than 18.3 and the device connects to networks with untrusted devices
-
Check macOS versionGo to System Settings > About (or System Preferences > About on older versions), or run 'sw_vers' in TerminalAffected if Version is earlier than 15.3 and the device is on a network where local attackers could send malicious network requests
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via MDM or Apple TV device managementAffected if Version is earlier than 18.3 and the Apple TV is connected to a network with untrusted devices
-
Check visionOS versionGo to Settings > About on Apple Vision Pro, or check via MDMAffected if Version is earlier than 2.3 and the device operates in shared or untrusted network environments
-
Check watchOS versionOpen Watch app on paired iPhone, go to General > About, or check via MDMAffected if Version is earlier than 11.3 and the Apple Watch connects to networks with potential attackers
You are affected if any Apple device runs an OS version below 18.3 (iOS/iPadOS/tvOS), 15.3 (macOS), 2.3 (visionOS), or 11.3 (watchOS) AND the device is accessible to an attacker on the local network.
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.311.315.3
Apply the vendor-supplied patches by updating all affected devices to iOS 18.3/iPadOS 18.3, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.3, or visionOS 2.3 respectively. For enterprise environments, deploy updates via MDM or software distribution tools.
iOS 18.3 / iPadOS 18.3 / macOS 15.3 / tvOS 18.3 / visionOS 2.3 / watchOS 11.3
- For iPhone: Upgrade to iOS 18.3 via Settings > General > Software Update
- For iPad: Upgrade to iPadOS 18.3 via Settings > General > Software Update
- For Mac: Upgrade to macOS Sequoia 15.3 (or macOS Sonoma 14.7.5 / macOS Ventura 13.7.5 for older systems) via System Settings > General > Software Update
- For Apple TV: Upgrade to tvOS 18.3 via Settings > General > Apple TV Software Update
- For Vision Pro: Upgrade to visionOS 2.3 via Settings > General > Software Update
- For Apple Watch: Upgrade to watchOS 11.3 via the Watch app on iPhone > General > Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24129 — 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-24129 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