CVE-2026-28867
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 with improved authentication. 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 Tahoe 26.4, tvOS 26.4, visionOS 26.4, watchOS 26.4. 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 · moderate confidenceThis vulnerability allowed a malicious or compromised application to bypass authentication checks and leak sensitive kernel state information. The issue was addressed through improved authentication mechanisms in the affected Apple operating systems, preventing unauthorized access to kernel-level data.
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>= 15.0, < 15.7.5>= 26.0, < 26.4< 26.4< 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
- 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 the device operating system versionOn iOS/iPadOS: Settings > General > About; On macOS: System Settings > General > About or run 'sw_vers'; On tvOS/watchOS/visionOS: Settings > General > AboutAffected if The installed version is less than 18.7.7 (for iOS/iPadOS), less than 15.7.5 or between 26.0 and 26.3 (for macOS), or less than 26.4 (for tvOS/watchOS/visionOS)
-
Verify MDM or update management statusFor managed devices, check the MDM console to confirm whether device compliance policies are enforced and OS update installations are being blocked or delayedAffected if The device is not receiving OS updates due to delayed rollout policies, skipped updates, or MDM configuration that defers security patches
-
Review installed applications for untrusted sourcesCheck the device for applications installed outside of the official App Store (iOS/iPadOS) or not signed by a known developer (macOS), as these could be the malicious vectors described in the CVEAffected if Applications from untrusted or unknown developers are installed, particularly if they request system-level or kernel access permissions
The device is affected if it runs an OS version below the fixed releases (iOS/iPadOS 18.7.7/26.4, macOS 15.7.5/26.4, tvOS/watchOS/visionOS 26.4) and has untrusted applications that could exploit the authentication bypass to leak kernel state information.
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 · scoped15.7.518.7.726.4
Users should update their devices to the fixed versions (iOS 18.7.7/26.4, iPadOS 18.7.7/26.4, macOS Sequoia 15.7.5/Tahoe 26.4, tvOS 26.4, visionOS 26.4, watchOS 26.4). Organizations should ensure mobile device management (MDM) policies enforce OS updates and review any custom applications that interact with system APIs.
iOS 18.7.7 or iOS 26.4 (iPhone); iPadOS 18.7.7 or iPadOS 26.4 (iPad); macOS Sequoia 15.7.5 or macOS Tahoe 26.4 (Mac); tvOS 26.4 (Apple TV); visionOS 26.4 (Vision Pro); watchOS 26.4 (Apple Watch)
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, Vision Pro, or Apple Watch)
- Check the current OS version on the device in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
- For iPhone/iPad: Upgrade to iOS 18.7.7 or iOS 26.4 / iPadOS 18.7.7 or iPadOS 26.4 depending on which major version line the device is on
- For Mac: Upgrade to macOS Sequoia 15.7.5 or macOS Tahoe 26.4 depending on which major version is installed
- For Apple TV: Upgrade to tvOS 26.4
- For Vision Pro: Upgrade to visionOS 26.4
- For Apple Watch: Upgrade to watchOS 26.4
- Install the update via Settings > General > Software Update (iOS/iPadOS/watchOS/tvOS/visionOS) or System Settings > General > Software Update (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-28867 — 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-28867 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