CVE-2026-28865
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 · uneditedAn authentication issue was addressed with improved state management. 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, tvOS 26.4, visionOS 26.4, watchOS 26.4. An attacker in a privileged network position may be able to intercept network traffic.
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 confidenceAuthentication state management flaw in Apple operating systems allows a man-in-the-middle attacker on the same network to intercept traffic by improperly handling authentication state transitions. The vulnerability is fixed in the listed point releases across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.
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.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 your iOS or iPadOS versionGo to Settings > General > About > Version on the deviceAffected if The version is less than 18.7.7 or greater than or equal to 26.0 but less than 26.4
-
Identify your macOS versionClick the Apple menu > About This Mac to view the macOS versionAffected if The version is 14.0 or greater but less than 14.8.5, OR 15.0 or greater but less than 15.7.5, OR 26.0 or greater but less than 26.4
-
Identify your tvOS, visionOS, or watchOS versionFor tvOS: Settings > General > About > Version. For visionOS: Settings > General > About > Version. For watchOS: On paired iPhone, open Watch app > My Watch > General > AboutAffected if For tvOS, visionOS, or watchOS: the version is less than 26.4
-
Assess network exposureDetermine whether the device connects to untrusted or shared networks (such as public Wi-Fi) where a man-in-the-middle attacker could be presentAffected if The device regularly connects to networks with untrusted or unknown users on the same network segment
You are affected if your Apple device runs an OS version that falls within any of the listed vulnerable ranges AND the device is used on networks where an attacker could intercept traffic.
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
Apply the appropriate Apple security update for your device: iOS 18.7.7/iPadOS 18.7.7 or iOS 26.4/iPadOS 26.4, macOS Sequoia 15.7.5/Sonoma 14.8.5/Tahoe 26.4, or the corresponding tvOS/visionOS/watchOS versions.
iOS 18.7.7 / iPadOS 18.7.7 / iOS 26.4 / iPadOS 26.4 / macOS Sonoma 14.8.5 / macOS Sequoia 15.7.5 / macOS Tahoe 26.4 / tvOS 26.4 / visionOS 26.4 / watchOS 26.4
- Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- Determine the current installed OS version from Settings > General > About (iOS/iPadOS/tvOS/watchOS/visionOS) or System Settings > General > About (macOS)
- For iPhone/iPad: If running iOS/iPadOS < 18.7.7, upgrade to 18.7.7; if running >= 26.0 and < 26.4, upgrade to 26.4
- For Mac: If running macOS Sonoma (14.x) < 14.8.5, upgrade to 14.8.5; if running macOS Sequoia (15.x) < 15.7.5, upgrade to 15.7.5; if running macOS Tahoe (26.x) < 26.4, upgrade to 26.4
- For Apple TV: Upgrade to tvOS 26.4
- For Apple Vision Pro: Upgrade to visionOS 26.4
- For Apple Watch: Upgrade to watchOS 26.4
- Perform upgrade via Settings > General > Software Update (iOS/iPadOS/tvOS/watchOS/visionOS) or System Settings > General > Software Update (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28865 — 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-28865 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