CVE-2026-28950
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 · uneditedA logging issue was addressed with improved data redaction. This issue is fixed in iOS 15.8.8 and iPadOS 15.8.8, iOS 16.7.16 and iPadOS 16.7.16, iOS 18.7.8 and iPadOS 18.7.8, iOS 26.4.2 and iPadOS 26.4.2, iPadOS 17.7.11. Notifications marked for deletion could be unexpectedly retained on the device.
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 confidenceThis is an iOS/iPadOS vulnerability where notifications marked for deletion are unexpectedly retained on the device due to a logging issue with improper data redaction. The flaw allows sensitive notification data to persist beyond the user's intended deletion action, creating a privacy exposure where deleted notifications may still be accessible.
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< 18.7.8>= 26.0, < 26.4.2< 18.7.8>= 26.0, < 26.4.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS versionGo to Settings > General > About and note the version number (e.g., 18.7.7, 26.3.1)Affected if Version is less than 18.7.8 OR falls between 26.0 and 26.4.2 inclusive
-
Check iPadOS versionGo to Settings > General > About and note the version numberAffected if Version is less than 18.7.8 OR falls between 26.0 and 26.4.2 inclusive
-
Identify if notifications were deletedSearch the device for any notification history or logs that may contain old notification contentAffected if Deleted notifications or notification data files exist on the device (the vulnerability causes them to be retained)
A user is affected if their device runs iOS/iPadOS version below 18.7.8 or between 26.0 and 26.4.2 and has notification data that was marked for deletion but may still be present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.7.826.4.2
Apply the relevant iOS/iPadOS security update for your version (15.8.8, 16.7.16, 17.7.11, 18.7.8, or 26.4.2) to ensure notifications are properly deleted when requested.
iOS 18.7.8 / iPadOS 18.7.8 (or latest applicable fixed version per your current iOS branch)
- Back up your iPhone or iPad using iCloud or Finder/iTunes
- Go to Settings > General > Software Update on your device
- Download and install the appropriate iOS/iPadOS version for your device: For iOS 18.x devices, install iOS 18.7.8; For iOS 17.x iPad-only devices, install iPadOS 17.7.11; For iOS 16.x devices, install iOS 16.7.16; For iOS 15.x devices, install iOS 15.8.8; For iOS 26.x devices, install iOS 26.4.2
- Verify the update was successful by checking Settings > General > About > iOS Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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