CVE-2026-28880
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 permissions issue was addressed with additional restrictions. This issue is fixed in iOS 18.7.7 and iPadOS 18.7.7, iOS 26.4 and iPadOS 26.4, macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.4, visionOS 26.4. An app may be able to enumerate a user's installed apps.
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 confidenceA permissions issue in Apple operating systems allowed a malicious or compromised application to enumerate a user's installed apps, bypassing intended app sandboxing restrictions. This privacy-sensitive information disclosure could enable reconnaissance for further attacks or privacy violations. The fix implemented additional restrictions to prevent unauthorized app enumeration.
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.7>= 26.0, < 26.4< 18.7.7>= 26.0, < 26.4>= 14.0, < 14.8.5>= 15.0, < 15.7.5>= 26.0, < 26.4< 26.4CVSS 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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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 Pro. For iOS devices, go to Settings > General > About. For macOS, go to System Settings > About or run 'sw_vers' in Terminal. For visionOS, go to Settings > About.Affected if Device runs any Apple operating system (iOS, iPadOS, macOS, visionOS)
-
Check iOS or iPadOS versionOn iPhone or iPad, open Settings > General > About and note the version number shown next to 'Software Version'.Affected if Version is less than 18.7.7, or falls between 26.0 and 26.4 (excluding 26.4)
-
Check macOS versionOpen System Settings > About or run 'sw_vers' in Terminal. Note the version number (for example, 14.5, 15.2, or 26.1).Affected if Version is 14.0 through 14.8.4, 15.0 through 15.7.4, or 26.0 through 26.3 (excluding 26.4)
-
Check visionOS versionOn Apple Vision Pro, go to Settings > About and note the software version.Affected if Version is any version below 26.4
-
Compare against affected version rangesMatch your discovered OS version against the vulnerable ranges: iOS/iPadOS < 18.7.7 or 26.0-26.3; macOS 14.0-14.8.4, 15.0-15.7.4, or 26.0-26.3; visionOS < 26.4.Affected if Installed version falls within any of the vulnerable version ranges
The environment is affected if the device runs any iOS, iPadOS, macOS, or visionOS version within the unpatched ranges: iOS/iPadOS < 18.7.7 or 26.0-26.3, macOS 14.0-14.8.4, 15.0-15.7.4, or 26.0-26.3, or visionOS < 26.4.
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.515.7.518.7.7
Update affected devices to the patched versions: iOS 18.7.7 or 26.4+, iPadOS 18.7.7 or 26.4+, macOS Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4+, or visionOS 26.4+. This is a standard OS update deployment.
iOS/iPadOS 18.7.7 or 26.4; macOS Sonoma 14.8.5, macOS Sequoia 15.7.5, or macOS Tahoe 26.4; visionOS 26.4
- Identify the device type (iPhone, iPad, Mac, or Apple Vision) and current OS version
- Back up the device data as a precaution before updating
- For iPhone/iPad: Navigate to Settings > General > Software Update and upgrade to iOS/iPadOS 18.7.7 or later (or 26.4 if on the 26.x branch)
- For Mac: Navigate to System Settings > General > Software Update and upgrade to macOS Sonoma 14.8.5, macOS Sequoia 15.7.5, or macOS Tahoe 26.4
- For Apple Vision: Navigate to Settings > General > Software Update and upgrade to visionOS 26.4
- Verify the update was successful by checking the OS version in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28880 — 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-28880 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