IpadosOperating system · Apple

CVE-2025-31233

MEDIUM · 6.3 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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, 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. Processing a maliciously crafted video file may lead to unexpected app termination or 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 · high confidence

A vulnerability in multiple Apple operating systems allows processing of maliciously crafted video files to trigger unexpected app termination or corrupt process memory due to insufficient input sanitization during video file parsing.

MitigationApply available Apple security updates (iOS 18.5, iPadOS 17.7.7+, macOS 13.7.6+/14.7.6+/15.5+, tvOS 18.5, visionOS 2.5, watchOS 11.5) to affected devices.

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

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

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 > Version and note the version number (e.g., 18.4)
    Affected if Version is less than 18.5 (e.g., 18.4, 18.3, 17.x series)
  2. Check iPadOS version on iPad
    Go to Settings > General > About > Version and note the version number
    Affected if Version is less than 17.7.7, OR version is 18.0 through 18.4.x
  3. Check macOS version on Mac
    Click Apple menu > About This Mac and note the version number (e.g., 15.4)
    Affected if Version is less than 13.7.6, OR version is 14.0 through 14.7.5, OR version is 15.0 through 15.4.x
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version and note the version number
    Affected if Version is less than 18.5 (e.g., 18.4, 18.3, 17.x series)
  5. Check watchOS version on Apple Watch
    On iPhone, open Watch app > General > About > Software Version and note the version
    Affected if Version is less than 11.5 (e.g., 11.4, 11.3, 10.x series)
  6. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About > Version and note the version number
    Affected if Version is less than 2.5 (e.g., 2.4, 2.3, 2.0, 1.x)

The environment is affected if the installed operating system version falls within any of the vulnerable version ranges listed for the respective Apple platform.

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 available Apple security updates (iOS 18.5, iPadOS 17.7.7+, macOS 13.7.6+/14.7.6+/15.5+, tvOS 18.5, visionOS 2.5, watchOS 11.5) to affected devices.

Recommended fix High confidence

iOS 18.5 / 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 (depending on device and current major version)

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
  2. Check the current installed OS version on the device
  3. For iPhone: upgrade to iOS 18.5 or later
  4. For iPad: upgrade to iPadOS 18.5 (if on iPadOS 18.x) or iPadOS 17.7.7 (if on iPadOS 17.x)
  5. For Mac: upgrade to macOS Sequoia 15.5, macOS Sonoma 14.7.6, or macOS Ventura 13.7.6 depending on which macOS major version is currently installed
  6. For Apple TV: upgrade to tvOS 18.5
  7. For Apple Vision Pro: upgrade to visionOS 2.5
  8. For Apple Watch: upgrade to watchOS 11.5
Caveat Standard Apple OS upgrade considerations apply - ensure backups exist and check app compatibility before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31233 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