dbcve.org
IpadosOperating system · Apple

CVE-2025-31234

HIGH · 8.2 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 15.5 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The issue was addressed with improved input sanitization. This issue is fixed in iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5. An attacker may be able to cause unexpected system termination or corrupt kernel 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

A kernel-level input validation vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) allows an attacker to corrupt kernel memory or cause system termination through insufficient input sanitization, likely in a kernel driver or system call handler.

MitigationApply the vendor-supplied patches (iOS 18.5, iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5) to address the input sanitization issue in the kernel.

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.5
Iphone OsOperating system
Affected:< 18.5
macOSOperating system
Affected:< 15.5
TvosOperating system
Affected:< 18.5
VisionosOperating system
Affected:< 2.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 look at the 'Software Version' field, or run `nsurlsessiond --version` to see the iOS version
    Affected if Version is lower than 18.5
  2. Check iPadOS version on iPad
    Go to Settings > General > About and look at the 'Software Version' field, or run `nsurlsessiond --version` to see the iPadOS version
    Affected if Version is lower than 18.5
  3. Check macOS version
    Click the Apple menu > About This Mac, or run `sw_vers` in Terminal, or run `system_profiler SPSoftwareDataType`
    Affected if Version is lower than 15.5 ( Sequoia 15.5 )
  4. Check tvOS version
    Go to Settings > General > About > Version, or check the build number in Settings > General > About
    Affected if Version is lower than 18.5
  5. Check visionOS version
    Go to Settings > About > Software Version, or check the Settings app on Apple Vision Pro
    Affected if Version is lower than 2.5

The device is affected if the installed operating system version is below the threshold (iOS/iPadOS/tvOS 18.5, macOS 15.5, or visionOS 2.5) for its product type.

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.5 / 15.5 / 18.5 or later
Fixed in 2.515.518.5
Interim mitigation

Apply the vendor-supplied patches (iOS 18.5, iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5) to address the input sanitization issue in the kernel.

Recommended fix High confidence

iOS 18.5/iPadOS 18.5 for iPhone/iPad; macOS Sequoia 15.5 for Mac; tvOS 18.5 for Apple TV; visionOS 2.5 for Vision Pro

  1. Identify the Apple device (iPhone, iPad, Mac, Apple TV, or Vision Pro) affected by this vulnerability
  2. Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Settings or System Preferences > About on macOS)
  3. Back up all important data before performing the update
  4. Update iPhone or iPad to iOS 18.5 or iPadOS 18.5 respectively via Settings > General > Software Update
  5. Update Mac to macOS Sequoia 15.5 via System Settings > General > Software Update
  6. Update Apple TV to tvOS 18.5 via Settings > System > Software Updates
  7. Update Apple Vision Pro to visionOS 2.5 via Settings > General > Software Update
  8. Verify the update was successful by checking the OS version in Settings > General > About
Caveat Standard minor version updates typically have minimal compatibility risks; ensure backups before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31234 — 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-31234 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