dbcve.org
IpadosOperating system · Apple

CVE-2025-43407

HIGH · 7.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 14.8.2 / 15.7.2 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
This issue was addressed with improved entitlements. This issue is fixed in iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1. An app may be able to break out of its sandbox.

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 sandbox escape vulnerability in multiple Apple operating systems where an app could break out of its sandbox due to improper entitlement configurations. The fix involved tightening and improving the entitlements to properly constrain app capabilities.

MitigationApply the vendor patches by updating to iOS 18.7.2/26.1, iPadOS 18.7.2/26.1, macOS Sequoia 15.7.2/Sonoma 14.8.2/Tahoe 26.1, tvOS 26.1, or visionOS 26.1 as appropriate. Developers should review app entitlements to ensure only minimal required permissions are requested.

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.1
Iphone OsOperating system
Affected:< 26.1
macOSOperating system
Affected:>= 14.0, < 14.8.2>= 15.0, < 15.7.2
TvosOperating system
Affected:< 26.1
VisionosOperating system
Affected:< 26.1

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. Identify your Apple device and OS type
    Determine whether you are running macOS, iOS, iPadOS, tvOS, or visionOS on your device. Each has different version numbering and affected ranges.
    Affected if The device runs any of the affected Apple operating systems.
  2. Check the installed iOS, iPadOS, tvOS, or visionOS version
    On iOS/iPadOS: go to Settings > General > About and note the Software Version. On tvOS/visionOS: go to Settings > General > About. Compare the version number to 26.1.
    Affected if The installed version is less than 26.1 on iOS, iPadOS, tvOS, or visionOS.
  3. Check the installed macOS version and build
    On Mac: choose Apple menu > About This Mac. Note the version (such as 14.x or 15.x). For precise comparison, click the version number to reveal the build number (such as 23xx).
    Affected if The macOS version is 14.0 through 14.8.2, or 15.0 through 15.7.2 (including any sub-builds within these ranges).
  4. Verify the specific macOS release name (optional)
    The About This Mac window displays the release name such as Sonoma (14.x) or Sequoia (15.x). Use this to identify which version range applies to your system.
    Affected if macOS is Sonoma (14.x) below 14.8.2, or Sequoia (15.x) below 15.7.2.

You are affected if your device runs iOS, iPadOS, tvOS, or visionOS earlier than version 26.1, or macOS Sonoma earlier than 14.8.2 or Sequoia earlier than 15.7.2.

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 14.8.2 / 15.7.2 / 26.1 or later
Fixed in 14.8.215.7.226.1
Interim mitigation

Apply the vendor patches by updating to iOS 18.7.2/26.1, iPadOS 18.7.2/26.1, macOS Sequoia 15.7.2/Sonoma 14.8.2/Tahoe 26.1, tvOS 26.1, or visionOS 26.1 as appropriate. Developers should review app entitlements to ensure only minimal required permissions are requested.

Recommended fix High confidence

iOS 18.7.2 / iPadOS 18.7.2 / macOS Sonoma 14.8.2 / macOS Sequoia 15.7.2 (or respective 26.1 versions for future major releases)

  1. For iPhone and iPad: Go to Settings > General > Software Update and update to iOS 18.7.2 / iPadOS 18.7.2 or later
  2. For macOS Sonoma (14.x): Go to System Settings > General > Software Update and update to macOS Sonoma 14.8.2 or later
  3. For macOS Sequoia (15.x): Go to System Settings > General > Software Update and update to macOS Sequoia 15.7.2 or later
  4. For Apple TV: Go to Settings > System > Software Updates and update to tvOS 26.1 or later when available
  5. For Apple Vision Pro: Go to Settings > General > Software Update and update to visionOS 26.1 or later when available
  6. After updating, verify the fix by checking Settings > General > About to confirm the installed OS version
Caveat Standard minor version updates typically include security fixes with minimal risk; backup device data before updating as a precaution

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-43407 — 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-43407 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