CVE-2025-24131
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 iOS 18.3 and iPadOS 18.3, iPadOS 17.7.6, 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 be able to cause a denial-of-service.
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 denial-of-service vulnerability in Apple operating systems stemming from improper memory handling. An attacker positioned on the local network can trigger the condition causing affected devices to become unresponsive or crash. The issue is addressed through improved memory management in the patched versions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 or iPadOS version on iPhones and iPadsGo to Settings > General > About on the device and look at the 'Version' fieldAffected if Version is less than 18.3 (for example, 18.2.x, 17.x, or earlier)
-
Check macOS version on MacsClick the Apple menu > About This Mac and view the macOS version shown (such as 15.2, 14.x, 13.x)Affected if Version is less than 15.3 (for example, 15.2.x, 14.x, 13.x)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV deviceAffected if Version is less than 18.3
-
Check visionOS version on Apple VisionGo to Settings > General > About on the Vision Pro device and note the version numberAffected if Version is less than 2.3
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone, go to My Watch > General > About, or on the watch go to Settings > General > AboutAffected if Version is less than 11.3
-
Assess network exposure for DoS vectorDetermine whether the device is connected to networks where untrusted parties could be present (local networks, public WiFi, guest networks)Affected if Vulnerable OS version AND device is on a network where an attacker could send malicious packets
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 is accessible to a local network attacker.
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 available security updates: iOS 18.3/iPadOS 18.3 or 17.7.6, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.3, or visionOS 2.3 depending on the device. For enterprise environments, deploy updates via MDM with testing to confirm stability.
iOS 18.3 / iPadOS 18.3 / macOS 15.3 / tvOS 18.3 / visionOS 2.3 / watchOS 11.3 (or iPadOS 17.7.6 for iPadOS 17.x devices)
- Identify the affected Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- For iPhones: Upgrade to iOS 18.3 or later
- For iPads: Upgrade to iPadOS 18.3 (or iPadOS 17.7.6 for older devices)
- For Macs: Upgrade to macOS Sequoia 15.3, macOS Sonoma 14.7.5, or macOS Ventura 13.7.5 depending on your current macOS version
- For Apple TV: Upgrade to tvOS 18.3
- For Apple Vision Pro: Upgrade to visionOS 2.3
- For Apple Watch: Upgrade to watchOS 11.3
- Back up device data before performing the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24131 — 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-24131 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