dbcve.org
IpadosOperating system · Apple

CVE-2025-31212

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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
This issue was addressed through improved state management. This issue is fixed in iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. An app may be able to access sensitive user data.

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 state management vulnerability in Apple platforms (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows a malicious or compromised application to access sensitive user data due to improper state handling between app components.

MitigationUpdate all affected Apple devices to the patched versions (iOS 18.5/iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5) to remediate the state management flaw.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 your Apple device and OS type
    Determine which Apple platform your device runs: iOS (iPhone), iPadOS (iPad), macOS (Mac computer), tvOS (Apple TV), visionOS (Apple Vision Pro), or watchOS (Apple Watch). Check the OS version in Settings > General > About (iOS/iPadOS), System Settings > About (macOS), Settings > General > About (tvOS), Settings > General > About (visionOS), or Settings > General > About (watchOS).
    Affected if The device runs any of the affected Apple OS types and the installed version is below the patched release.
  2. Verify iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number. Compare this to 18.5.
    Affected if The installed iOS or iPadOS version is lower than 18.5.
  3. Verify macOS version
    On Mac, click the Apple menu > About This Mac and note the version number. Compare this to 15.5 (macOS Sequoia 15.5).
    Affected if The installed macOS version is lower than 15.5.
  4. Verify tvOS version
    On Apple TV, go to Settings > General > About and note the version number. Compare this to 18.5.
    Affected if The installed tvOS version is lower than 18.5.
  5. Verify visionOS version
    On Apple Vision Pro, go to Settings > General > About and note the version number. Compare this to 2.5.
    Affected if The installed visionOS version is lower than 2.5.
  6. Verify watchOS version
    On Apple Watch, open the Settings app on the watch, go to General > About, or pair with iPhone and check in the Watch app under General > About. Note the version number and compare to 11.5.
    Affected if The installed watchOS version is lower than 11.5.

You are affected if your device runs any of the affected Apple platforms and the installed OS version is below the minimum patched version (iOS/iPadOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5).

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 / 15.5 or later
Fixed in 2.511.515.5
Interim mitigation

Update all affected Apple devices to the patched versions (iOS 18.5/iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5) to remediate the state management flaw.

Recommended fix High confidence

iOS 18.5, iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5

  1. For iPhone users: Go to Settings > General > Software Update and install iOS 18.5
  2. For iPad users: Go to Settings > General > Software Update and install iPadOS 18.5
  3. For Mac users: Go to System Settings > General > Software Update and install macOS Sequoia 15.5
  4. For Apple TV users: Go to Settings > System > Software Updates and install tvOS 18.5
  5. For Apple Vision Pro users: Go to Settings > General > Software Update and install visionOS 2.5
  6. For Apple Watch users: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 11.5
Caveat Standard OS upgrade risks apply - verify app compatibility before updating production devices

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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