dbcve.org
IpadosOperating system · Apple

CVE-2026-65329

MEDIUM · 5.9 CVSS v3.1 Published 2026-08-17
Fix available
A fix is available. Upgrade to 26.6.1 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges Zero-click Brand new

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 · unedited
An authentication issue was addressed with improved state management. This issue is fixed in iOS 26.6.1 and iPadOS 26.6.1. An attacker in a privileged network position may be able to bypass IPSec authentication and 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
How this class of weakness works · CWE-287

The mechanism that verifies who a user is can be side-stepped or fooled, letting an attacker act as someone they're not. Everything built on top of that identity then becomes untrustworthy. Fixing it means hardening the full authentication flow, including edge cases, tokens, and secondary paths.

General guidance for the improper authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
IpadosOperating system
Affected:< 26.6.1
Iphone OsOperating system
Affected:< 26.6.1

CVSS 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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

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 · scoped
Upgrade available Upgrade to 26.6.1 or later
Fixed in 26.6.1
Recommended fix Moderate confidence

iOS 26.6.1 and iPadOS 26.6.1

  1. 1. Backup your device data to iCloud or a computer before updating
  2. 2. Connect your iPhone or iPad to Wi-Fi and ensure at least 50% battery or connect to power
  3. 3. Go to Settings > General > Software Update
  4. 4. Download and install iOS 26.6.1 or iPadOS 26.6.1 when available
  5. 5. After installation, verify the update by checking Settings > General > About > Version
Caveat Major iOS version upgrades may include UI changes, removal of older app compatibility, or require re-authentication to services

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $4,000. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-65329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-65329 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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