dbcve.org
IpadosOperating system · Apple

CVE-2025-31221

HIGH · 7.5 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
84/100
Remediation priority · High
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
An integer overflow was addressed with improved input validation. This issue is fixed in iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6, tvOS 18.5, visionOS 2.5, watchOS 11.5. A remote attacker may be able to leak 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 · high confidence

An integer overflow vulnerability in Apple's platform software allows a remote attacker to leak memory due to insufficient input validation. The issue affects multiple Apple operating systems across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.

MitigationApply the vendor-supplied security updates: update to iOS 18.5/iPadOS 18.5/17.7.7, macOS Sequoia 15.5/Sonoma 14.7.6/Ventura 13.7.6, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate for each affected device.

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:< 17.7.7>= 18.0, < 18.5
Iphone OsOperating system
Affected:< 18.5
macOSOperating system
Affected:< 13.7.6>= 14.0, < 14.7.6>= 15.0, < 15.5
TvosOperating system
Affected:< 18.5
VisionosOperating system
Affected:< 2.5
WatchosOperating system
Affected:< 11.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify iOS or iPadOS version
    Go to Settings > General > About and note the Version number
    Affected if Version is below 17.7.7, OR version is 18.0 through 18.4.x (18.5 and above are fixed)
  2. Identify macOS version
    Go to System Settings > General > About (or System Preferences > About on older macOS) and note the Version number
    Affected if Version is below 13.7.6, OR between 14.0 and 14.7.5, OR between 15.0 and 15.4.x (13.7.6+, 14.7.6+, or 15.5+ are fixed)
  3. Identify tvOS version
    Go to Settings > General > About > Version
    Affected if Version is below 18.5 (18.5 and above are fixed)
  4. Identify visionOS version
    Go to Settings > General > About > Version
    Affected if Version is below 2.5 (2.5 and above are fixed)
  5. Identify watchOS version
    Go to Settings > General > About > Version on the Watch app on iPhone, or on the watch go to Settings > General > About
    Affected if Version is below 11.5 (11.5 and above are fixed)

You are affected if your device runs any of the Apple OS versions listed above that fall within the vulnerable ranges; the vulnerability is in the platform software itself and requires no specific feature to be enabled for a remote attacker to trigger the integer overflow.

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 / 11.5 / 13.7.6 or later
Fixed in 2.511.513.7.6
Interim mitigation

Apply the vendor-supplied security updates: update to iOS 18.5/iPadOS 18.5/17.7.7, macOS Sequoia 15.5/Sonoma 14.7.6/Ventura 13.7.6, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate for each affected device.

Recommended fix High confidence

Upgrade to iOS 18.5/iPadOS 18.5/iPadOS 17.7.7, macOS Ventura 13.7.6/macOS Sonoma 14.7.6/macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate for your device

  1. Check current device OS version in Settings > General > About (iOS/iPadOS/watchOS/tvOS/visionOS) or System Settings > General > About (macOS)
  2. Ensure device is connected to Wi-Fi and has sufficient battery (or connect to power)
  3. Back up important data using iCloud or computer backup
  4. For iOS/iPadOS: Go to Settings > General > Software Update and install the available update
  5. For macOS: Go to System Settings > General > Software Update and install the available update
  6. For tvOS: Go to Settings > General > About > Software Update
  7. For watchOS: On iPhone, open Watch app > General > Software Update
  8. For visionOS: Go to Settings > General > Software Update
Caveat Standard OS update risks apply; major version jumps (e.g., iOS 17 to 18) may have app compatibility considerations

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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