dbcve.org
IpadosOperating system · Apple

CVE-2026-20680

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 14.8.4 / 15.7.4 or later.
See remediation →
67/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
The issue was addressed with additional restrictions on the observability of app states. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3. A sandboxed 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 · high confidence

A sandboxed application could access sensitive user data due to insufficient restrictions on the observability of app states. The vulnerability allowed a confined app to potentially leak or access information it should not have permission to view. The fix implements additional restrictions to properly isolate sandboxed processes.

MitigationUpdate affected devices to iOS 18.7.5/iOS 26.3, iPadOS 18.7.5/iPadOS 26.3, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, or macOS Tahoe 26.3 or later to apply the OS-level restrictions.

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.7.5>= 26.0, < 26.3
Iphone OsOperating system
Affected:< 18.7.5>= 26.0, < 26.3
macOSOperating system
Affected:< 14.8.4>= 15.0, < 15.7.4>= 26.0, < 26.3

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 the installed iPadOS version
    Go to Settings > General > About on the iPad and note the version number. Compare it to the affected ranges: < 18.7.5 or >= 26.0 and < 26.3
    Affected if The installed version falls within < 18.7.5 or >= 26.0, < 26.3
  2. Identify the installed iPhone OS version
    Go to Settings > General > About on the iPhone and note the version number. Compare it to the affected ranges: < 18.7.5 or >= 26.0 and < 26.3
    Affected if The installed version falls within < 18.7.5 or >= 26.0, < 26.3
  3. Identify the installed macOS version
    Click the Apple menu > About This Mac and note the version number. Compare it to the affected ranges: < 14.8.4, >= 15.0 and < 15.7.4, or >= 26.0 and < 26.3
    Affected if The installed version falls within < 14.8.4, >= 15.0 and < 15.7.4, or >= 26.0, < 26.3
  4. Confirm sandboxed applications exist on the device
    Review installed applications from the home screen or Applications folder. All third-party App Store applications run within sandbox containers on iOS/iPadOS by default
    Affected if Any third-party applications are installed and running on the device

The environment is affected if the device runs any affected iOS/iPadOS version (< 18.7.5 or >= 26.0, < 26.3) or macOS version (< 14.8.4, >= 15.0 and < 15.7.4, or >= 26.0, < 26.3) and has sandboxed applications installed.

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.4 / 15.7.4 / 18.7.5 or later
Fixed in 14.8.415.7.418.7.5
Interim mitigation

Update affected devices to iOS 18.7.5/iOS 26.3, iPadOS 18.7.5/iPadOS 26.3, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, or macOS Tahoe 26.3 or later to apply the OS-level restrictions.

Recommended fix High confidence

iPadOS 18.7.5/26.3, iOS 18.7.5/26.3, macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, or macOS Tahoe 26.3

  1. For iPadOS: Go to Settings > General > Software Update and upgrade to iPadOS 18.7.5 or later (or iPadOS 26.3 if your device supports it)
  2. For iPhone: Go to Settings > General > Software Update and upgrade to iOS 18.7.5 or later (or iOS 26.3 if your device supports it)
  3. For macOS: Open System Settings > General > Software Update and upgrade to macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, or macOS Tahoe 26.3 as appropriate for your device

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-2026-20680 — 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-2026-20680 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