CVE-2026-64739
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 out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6 and iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, watchOS 26.6. An attacker may be able to cause unexpected app termination.
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 confidenceThis is a memory safety vulnerability where an out-of-bounds write occurs due to insufficient bounds checking. An attacker can trigger this flaw to write data beyond allocated buffer boundaries, leading to memory corruption that causes unexpected application termination.
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.6< 26.6>= 14.0, < 14.8.8>= 15.0, < 15.7.8>= 26.0, < 26.6< 26.6< 26.6< 26.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Check iOS version on iPhoneOn the iPhone, go to Settings > General > About > Version. Alternatively, connect to a computer with iTunes or Finder and check the device info, or query via MDM using the 'OSVersion' or 'ProductVersion' attribute.Affected if The version is below 26.6 (for example, 26.5.x or earlier)
-
Check iPadOS version on iPadOn the iPad, go to Settings > General > About > Version. Alternatively, connect to a computer with iTunes or Finder and check the device info, or query via MDM using the 'OSVersion' or 'ProductVersion' attribute.Affected if The version is below 26.6 (for example, 26.5.x or earlier)
-
Check macOS versionClick the Apple menu > About This Mac. The version number appears below the macOS name. Alternatively, run 'sw_vers -productVersion' in Terminal, or query via MDM/Jamf using the 'OSVersion' attribute.Affected if The version is 14.0 to 14.8.7, 15.0 to 15.7.7, or 26.0 to 26.5.x (falling within any of the three vulnerable ranges)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV. Alternatively, query via MDM using the 'OSVersion' or 'SoftwareVersion' attribute.Affected if The version is below 26.6 (for example, 26.5.x or earlier)
-
Check visionOS version on Apple Vision ProGo to Settings > General > About > Version on the device. Alternatively, query via MDM using the 'OSVersion' or 'ProductVersion' attribute.Affected if The version is below 26.6 (for example, 26.5.x or earlier)
-
Check watchOS version on Apple WatchOn the Apple Watch, go to Settings > General > About > Version. On the paired iPhone, open the Watch app > My Watch > General > About. Alternatively, query via MDM using the 'OSVersion' attribute.Affected if The version is below 26.6 (for example, 26.5.x or earlier)
You are affected if any of your Apple devices (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch) run a version lower than the minimum fixed version for their respective platform.
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.815.7.826.6
Update affected Apple devices to the patched versions: iOS/iPadOS 18.7.10 or 26.6+, macOS Sequoia 15.7.8+, macOS Sonoma 14.8.8+, macOS Tahoe 26.6+, tvOS 26.6+, visionOS 26.6+, or watchOS 26.6+.
iOS 26.6/iPadOS 26.6, macOS Sonoma 14.8.8+, macOS Sequoia 15.7.8+, macOS Tahoe 26.6+, tvOS 26.6, visionOS 26.6, watchOS 26.6
- For iPhone and iPad users: Go to Settings > General > Software Update and upgrade to iOS 26.6 or iPadOS 26.6
- For Mac users: Open System Settings > General > Software Update and upgrade to the appropriate version (macOS Sonoma 14.8.8+, macOS Sequoia 15.7.8+, or macOS Tahoe 26.6+)
- For Apple TV users: Go to Settings > System > Software Updates and upgrade to tvOS 26.6
- For Apple Watch users: Open the Watch app on iPhone, go to General > Software Update and upgrade to watchOS 26.6
- For Vision Pro users: Go to Settings > General > Software Update and upgrade to visionOS 26.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-64739 — 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-64739 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