dbcve.org
IpadosOperating system · Apple

CVE-2025-43347

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 26.0 or later.
See remediation →
100/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
This issue was addressed by removing the vulnerable code. This issue is fixed in iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. An input validation issue was addressed.

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

This is an input validation vulnerability in Apple operating systems (iOS, iPadOS, macOS Tahoe, tvOS, visionOS, watchOS 26) that was addressed by removing the vulnerable code. The CRITICAL CVSS 9.8 score indicates potential for remote code execution or severe system compromise via malformed input.

MitigationApply the vendor patches by updating all affected Apple devices to iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26 respectively.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 version on iPhone
    Open Settings > General > About > Version, or use an MDM solution or Apple Configurator to query the device
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)
  2. Check iPadOS version on iPad
    Open Settings > General > About > Version, or use an MDM solution or Apple Configurator to query the device
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)
  3. Check macOS version on Mac
    Run 'sw_vers -productVersion' in Terminal, or go to Apple menu > About This Mac
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)
  4. Check tvOS version on Apple TV
    Navigate to Settings > General > About > Version, or use MDM to query the device
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)
  5. Check visionOS version on Vision Pro
    Navigate to Settings > General > About > Version, or use MDM to query the device
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)
  6. Check watchOS version on Apple Watch
    On paired iPhone, open Watch app > General > About, or use MDM to query the device
    Affected if Version is below 26.0 (e.g., 25.x, 24.x, etc.)

If any Apple device (iPhone, iPad, Mac, Apple TV, Vision Pro, or Apple Watch) is running an OS version below 26.0, the environment is affected by this input validation vulnerability.

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 the vendor patches by updating all affected Apple devices to iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26 respectively.

Recommended fix High confidence

iOS 26.0, iPadOS 26.0, macOS Tahoe 26.0, tvOS 26.0, visionOS 26.0, watchOS 26.0

  1. On iPhone/iPad: Go to Settings > General > Software Update and install iOS 26.0 / iPadOS 26.0
  2. On Mac: Open System Settings > Software Update and install macOS Tahoe 26.0
  3. On Apple TV: Go to Settings > System > Software Updates and install tvOS 26.0
  4. On Apple Watch: Open the Watch app on iPhone > My Watch > General > Software Update and install watchOS 26.0
  5. On Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26.0
  6. After updating, verify the update was successful by checking the OS version in Settings > General > About
Caveat Major OS upgrades may have app compatibility considerations; review app vendor compatibility notes before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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