CVE-2026-28993
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 · uneditedThis issue was addressed by adding an additional prompt for user consent. 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, visionOS 26.5. An app may be able to access user-sensitive 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 · moderate confidenceThis vulnerability allowed an application to access user-sensitive data without proper authorization. The fix involved adding an additional user consent prompt, indicating the issue was a missing or insufficient permission check that could be bypassed. The CVSS 5.5 score suggests low attack complexity with high confidentiality impact but no integrity impact.
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.9>= 26.0, < 26.5< 18.7.9>= 26.0, < 26.5>= 14.0, < 14.8.7>= 15.0, < 15.7.7>= 26.0, < 26.5< 26.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify device type and operating systemDetermine whether the device is an iPhone, iPad, Mac, or Apple Vision. On iPhone/iPad: go to Settings > General > About. On Mac: click Apple menu > About This Mac. On Vision: go to Settings > General > About.Affected if Device is an Apple device running iOS, iPadOS, macOS, or visionOS
-
Check iOS version on iPhoneOn iPhone, go to Settings > General > About and note the software version number displayed next to 'Version'.Affected if Version is less than 18.7.9 OR version is 26.0 through 26.4
-
Check iPadOS version on iPadOn iPad, go to Settings > General > About and note the software version number displayed next to 'Version'.Affected if Version is less than 18.7.9 OR version is 26.0 through 26.4
-
Check macOS versionOn Mac, click Apple menu > About This Mac and note the version number (such as 14.x, 15.x, or 26.x) displayed under the macOS name.Affected if Version is 14.0 through 14.8.6, 15.0 through 15.7.6, or 26.0 through 26.4
-
Check visionOS versionOn Apple Vision, go to Settings > General > About and note the version number displayed next to 'Version'.Affected if Version is less than 26.5
The device is affected if it is an Apple device running any version within the specified ranges: iOS/iPadOS below 18.7.9 or between 26.0-26.4, macOS between 14.0-14.8.6, 15.0-15.7.6, or 26.0-26.4, or visionOS below 26.5.
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 · scoped14.8.715.7.718.7.9
Update affected Apple devices to the fixed versions (iOS 18.7.9/26.5, iPadOS 18.7.9/26.5, macOS Sequoia 15.7.7, Sonoma 14.8.7, Tahoe 26.5, visionOS 26.5). For custom applications, review and enforce proper permission request flows following Apple's Human Interface Guidelines.
iOS 18.7.9/iPadOS 18.7.9 or iOS 26.5/iPadOS 26.5 (depending on current branch); macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, or macOS Tahoe 26.5 (depending on current branch); visionOS 26.5
- 1. Identify the current version of the Apple device (iOS, iPadOS, macOS, or visionOS) by going to Settings > General > About on iOS/iPadOS, or System Settings/About This Mac on macOS, or Settings > General > About on visionOS.
- 2. Determine which product line and current major version is running (e.g., iOS 18.x, iOS 26.x, macOS 14.x Sonoma, macOS 15.x Sequoia, visionOS).
- 3. For iPhone/iPad: If running iOS/iPadOS < 18.7.9, upgrade to iOS 18.7.9 or iPadOS 18.7.9. If running >= 26.0 and < 26.5, upgrade to iOS 26.5 or iPadOS 26.5.
- 4. For Mac: If running macOS 14.x (Sonoma), upgrade to 14.8.7. If running macOS 15.x (Sequoia), upgrade to 15.7.7. If running >= 26.0 and < 26.5, upgrade to macOS Tahoe 26.5.
- 5. For Vision Pro: If running visionOS < 26.5, upgrade to visionOS 26.5.
- 6. Perform the update via Settings > General > Software Update on iOS/iPadOS/visionOS, or System Settings > General > Software Update on macOS.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28993 — 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-28993 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