dbcve.org
IpadosOperating system · Apple

CVE-2025-43372

HIGH · 7.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 26.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 validation. This issue is fixed in iOS 26 and iPadOS 26, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. Processing a maliciously crafted media 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

Memory corruption vulnerability in media file parsing due to insufficient input validation. Processing maliciously crafted media files can trigger buffer overflows or similar memory corruption, leading to app termination or potentially arbitrary code execution.

MitigationApply vendor patches (iOS 26, iPadOS 26, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26). Until patched, avoid opening media files from untrusted sources.

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:< 26.0
Iphone OsOperating system
Affected:< 26.0
macOSOperating system
Affected:< 26.0
TvosOperating system
Affected:< 26.0
VisionosOperating system
Affected:< 26.0
WatchosOperating system
Affected:< 26.0

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 or iPadOS version
    Go to Settings > General > About > Version. Compare the version number to 26.0. On iOS/iPadOS, the version will show as something like 25.x.x
    Affected if The device runs iOS or iPadOS version lower than 26.0
  2. Check macOS version
    Go to System Settings > About (or Apple menu > About This Mac). Compare the version number to 26.0. macOS versions are named (Sonoma, Tahoe, etc.) with a number like 14.x.x
    Affected if The device runs macOS version lower than 26.0 (or older than 14.8.2 for Sonoma)
  3. Check tvOS version
    Go to Settings > General > About > Version. Compare the version number to 26.0
    Affected if The device runs tvOS version lower than 26.0
  4. Check watchOS version
    Go to Settings > General > About > Version on the Apple Watch, or through the Watch app on iPhone. Compare the version number to 26.0
    Affected if The device runs watchOS version lower than 26.0
  5. Check visionOS version
    Go to Settings > General > About > Version. Compare the version number to 26.0
    Affected if The device runs visionOS version lower than 26.0
  6. Identify media file processing usage
    Review any applications or services that automatically process or parse media files from external or untrusted sources. This includes image viewers, video players, audio tools, or any app that loads media attachments
    Affected if Media files from untrusted sources are processed on an unpatched device

A device is affected if it runs any Apple operating system version below 26.0 (or macOS Sonoma below 14.8.2) and processes maliciously crafted media files from untrusted sources.

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 26.0 or later
Fixed in 26.0
Interim mitigation

Apply vendor patches (iOS 26, iPadOS 26, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26). Until patched, avoid opening media files from untrusted sources.

Recommended fix High confidence

iOS 26, iPadOS 26, macOS Sonoma 14.8.2, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26 (depending on device type)

  1. Check current device OS version in Settings > General > About (iOS/iPadOS/watchOS/tvOS/visionOS) or System Settings > About (macOS)
  2. Ensure important data is backed up to iCloud or computer before upgrading
  3. Install the latest available update: iOS 26 or iPadOS 26 for iPhone/iPad devices, macOS Sonoma 14.8.2 or macOS Tahoe 26 for Mac computers, tvOS 26 for Apple TV, visionOS 26 for Apple Vision Pro, or watchOS 26 for Apple Watch
  4. Restart the device after the update is installed to ensure all security fixes are fully applied
Caveat OS updates may introduce UI changes or remove support for older apps; review release notes 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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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