dbcve.org
IpadosOperating system · Apple

CVE-2025-24126

HIGH · 7.3 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 2.3 / 11.3 or later.
See remediation →
75/100
Remediation priority · High
Zero-click

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 · unedited
An input validation issue was addressed. 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 be able to corrupt process memory.

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 confidence

This is an input validation vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) that allows an attacker on the local network to corrupt process memory through malformed network input, potentially leading to code execution or denial of service.

MitigationUpdate all affected Apple devices to the patched versions: 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 or later.

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
IpadosOperating system
Affected:< 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 15.3
TvosOperating system
Affected:< 18.3
VisionosOperating system
Affected:< 2.3
WatchosOperating system
Affected:< 11.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version on iPhone
    Go to Settings > General > About and note the version number under 'Software Version'
    Affected if The version shown is lower than 18.3 (for example, 18.2.x, 17.x, or earlier)
  2. Check iPadOS version on iPad
    Go to Settings > General > About and note the version number under 'Software Version'
    Affected if The version shown is lower than 18.3 (for example, 18.2.x, 17.x, or earlier)
  3. Check macOS version on Mac
    Click Apple menu > About This Mac and note the version number under macOS (for example, 15.2, 14.x, 13.x)
    Affected if The version shown is lower than 15.3 (for example, 15.2.x, 14.x, 13.x)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version and note the software version number
    Affected if The version shown is lower than 18.3 (for example, 18.2.x or earlier)
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > About > Software Version or ask Siri 'What version is visionOS?'
    Affected if The version shown is lower than 2.3 (for example, 2.2.x or earlier)
  6. Check watchOS version on Apple Watch
    On the watch, go to Settings > General > About > Software Version, or open the Watch app on iPhone and go to My Watch > General > About
    Affected if The version shown is lower than 11.3 (for example, 11.2.x or earlier)

The device is affected if it is running any version of iOS, iPadOS, macOS, tvOS, visionOS, or watchOS lower than the patched versions (18.3, 15.3, 2.3, or 11.3 respectively) and has network connectivity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3 / 11.3 / 15.3 or later
Fixed in 2.311.315.3
Interim mitigation

Update all affected Apple devices to the patched versions: 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 or later.

Recommended fix High confidence

Minimum fixed versions: iOS 18.3, iPadOS 18.3, macOS 15.3 (Sequoia)/14.7.5 (Sonoma)/13.7.5 (Ventura), tvOS 18.3, visionOS 2.3, watchOS 11.3

  1. For iPhone users: Upgrade to iOS 18.3 or later via Settings > General > Software Update
  2. For iPad users: Upgrade to iPadOS 18.3 or later via Settings > General > Software Update
  3. For Mac users: Upgrade to macOS Sequoia 15.3, macOS Sonoma 14.7.5, or macOS Ventura 13.7.5 via System Settings > General > Software Update
  4. For Apple TV users: Upgrade to tvOS 18.3 or later via Settings > General > Apple TV Software Update
  5. For Vision Pro users: Upgrade to visionOS 2.3 or later via Settings > General > Software Update
  6. For Apple Watch users: Upgrade to watchOS 11.3 or later via the Watch app on iPhone

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24126 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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