CVE-2026-28855
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 26.3 and iPadOS 26.3, macOS Tahoe 26.3. An app may be able to access protected 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 · moderate confidenceThis is a permissions bypass vulnerability in iOS 26.3, iPadOS 26.3, and macOS Tahoe 26.3 where an application could improperly access protected user data due to insufficient restrictions on sensitive data access controls.
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< 26.3< 26.3>= 26.0, < 26.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneGo to Settings > General > About on the device and look at the Version fieldAffected if Version number is less than 26.3 (for example, 26.2.x or earlier)
-
Check iPadOS version on iPadGo to Settings > General > About on the device and look at the Version fieldAffected if Version number is less than 26.3 (for example, 26.2.x or earlier)
-
Check macOS Tahoe versionOpen System Settings > About or run 'sw_vers' in Terminal and check the Marketing VersionAffected if Version is 26.0 or higher but lower than 26.3 (for example, 26.1.x or 26.2.x)
-
Identify applications with sensitive data accessReview installed applications and check which apps have been granted access to Privacy-sensitive categories (Contacts, Photos, Location, etc.) in System Settings > Privacy & SecurityAffected if Any third-party application has been granted access to protected user data categories and the OS version is in the affected range
A user is affected if their device runs iOS, iPadOS, or macOS Tahoe version 26.0 through 26.2.x (i.e., any version below 26.3).
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 · scoped26.3
Update affected devices to iOS 26.3, iPadOS 26.3, or macOS Tahoe 26.3 or later to apply the additional permission restrictions that address this vulnerability.
iOS 26.3 for iPhone, iPadOS 26.3 for iPad, macOS Tahoe 26.3 for Mac
- For iPhone: Go to Settings > General > Software Update and install iOS 26.3
- For iPad: Go to Settings > General > Software Update and install iPadOS 26.3
- For Mac: Go to System Settings > General > Software Update and install macOS Tahoe 26.3
- Alternatively, use Finder (iPhone/iPad) or System Preferences (Mac) to update via wired connection for more reliable updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28855 — 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-28855 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