dbcve.org
IpadosOperating system · Apple

CVE-2026-28987

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 14.8.7 / 15.7.7 or later.
See remediation →
84/100
Remediation priority · High
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
A logging issue was addressed with improved data redaction. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5, tvOS 26.5, watchOS 26.5. An app may be able to leak sensitive kernel state.

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

This is a logging vulnerability where insufficient data redaction in system logs allowed an application to leak sensitive kernel state information. The issue stemmed from improper handling of sensitive data during logging operations in Apple's kernel subsystems.

MitigationApply the vendor-supplied patches by updating to iOS 18.7.9/iPadOS 18.7.9 or later, iOS 26.5/iPadOS 26.5 or later, macOS Sequoia 15.7.7/Sonoma 14.8.7/Tahoe 26.5 or later, tvOS 26.5 or later, and watchOS 26.5 or later.

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.9>= 26.0, < 26.5
Iphone OsOperating system
Affected:< 18.7.9>= 26.0, < 26.5
macOSOperating system
Affected:>= 14.0, < 14.8.7>= 15.0, < 15.7.7>= 26.0, < 26.5
TvosOperating system
Affected:< 26.5
WatchosOperating system
Affected:< 26.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 your iOS or iPadOS version
    On the device, go to Settings > General > About and note the Version number
    Affected if The version is less than 18.7.9, or is 26.0 through 26.4 (i.e., 26.0 <= version < 26.5)
  2. Identify your macOS version
    Go to System Settings > About (or Apple menu > About This Mac) and note the version number shown
    Affected if The version is 14.0 through 14.8.6, 15.0 through 15.7.6, or 26.0 through 26.4 (i.e., version matches 14.x where x<8.7, 15.x where x<7.7, or 26.x where x<5)
  3. Identify your tvOS version
    Go to Settings > General > About and note the Version number
    Affected if The version is less than 26.5 (i.e., any version before 26.5)
  4. Identify your watchOS version
    Go to Settings > General > About on the watch and note the Version number
    Affected if The version is less than 26.5 (i.e., any version before 26.5)

You are affected if your device runs any of the Apple OS versions listed in the affected ranges for your specific device type.

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.7 / 15.7.7 / 18.7.9 or later
Fixed in 14.8.715.7.718.7.9
Interim mitigation

Apply the vendor-supplied patches by updating to iOS 18.7.9/iPadOS 18.7.9 or later, iOS 26.5/iPadOS 26.5 or later, macOS Sequoia 15.7.7/Sonoma 14.8.7/Tahoe 26.5 or later, tvOS 26.5 or later, and watchOS 26.5 or later.

Recommended fix High confidence

Upgrade to iOS/iPadOS 18.7.9 or 26.5, macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, or macOS Tahoe 26.5, tvOS 26.5, or watchOS 26.5 depending on current OS branch

  1. Identify the affected Apple device type (iPhone, iPad, Mac, Apple TV, or Apple Watch)
  2. Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Settings > About on macOS, Settings > General on tvOS/watchOS)
  3. Back up the device using iCloud or local backup before updating
  4. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18.7.9 or iPadOS 18.7.9 (for 18.x users), or iOS 26.5/iPadOS 26.5 (for 26.x users)
  5. For Mac: Go to System Settings > Software Update and install macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, or macOS Tahoe 26.5 as appropriate
  6. For Apple TV: Go to Settings > System > Software Updates and install tvOS 26.5
  7. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone and install watchOS 26.5
  8. Verify the update was successful by checking the OS version again
Caveat Standard OS update risks apply (potential for app incompatibility, data migration issues); ensure backup before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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