CVE-2026-20611
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 access issue was addressed with improved bounds checking. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, watchOS 26.3. Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory.
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 confidenceAn out-of-bounds access vulnerability exists in Apple's media processing frameworks (likely in a media codec or parser). The vulnerability allows processing of a maliciously crafted media file to trigger memory corruption or application termination due to insufficient bounds checking during media parsing.
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.5>= 26.0, < 26.3< 18.7.5>= 26.0, < 26.3< 14.8.4>= 15.0, < 15.7.4>= 26.0, < 26.3< 26.3< 26.3< 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 iPhonesGo to Settings > General > About on the iPhone and note the iOS version numberAffected if The installed iOS version is less than 18.7.5, or is 26.0, 26.1, or 26.2
-
Check iPadOS version on iPadsGo to Settings > General > About on the iPad and note the iPadOS version numberAffected if The installed iPadOS version is less than 18.7.5, or is 26.0, 26.1, or 26.2
-
Check macOS version on MacsClick the Apple menu > About This Mac and note the macOS version numberAffected if The installed macOS version is less than 14.8.4, or is between 15.0 and 15.7.3 inclusive, or is 26.0, 26.1, or 26.2
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on Apple TVAffected if The installed tvOS version is less than 26.3
-
Check visionOS version on Vision ProGo to Settings > General > About on Vision Pro and note the visionOS versionAffected if The installed visionOS version is less than 26.3
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone, go to General > About, or go to Settings > General > About on the Apple Watch itselfAffected if The installed watchOS version is less than 26.3
A device is affected if its operating system version falls within any of the listed vulnerable ranges and it processes media files using Apple's native media frameworks.
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.415.7.418.7.5
Apply the Apple security updates for the relevant platform (iOS 18.7.5/26.3, iPadOS 18.7.5/26.3, macOS 15.7.4/14.8.4/26.3, tvOS 26.3, visionOS 26.3, or watchOS 26.3) to all affected devices. For custom applications using Apple's media frameworks, review media parsing code and implement proper bounds validation.
iOS 18.7.5/iPadOS 18.7.5 (or iOS 26.3/iPadOS 26.3 for newer devices), macOS Sonoma 14.8.4/macOS Sequoia 15.7.4/macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, watchOS 26.3
- For iPhone and iPad: Go to Settings > General > Software Update and install iOS 18.7.5 or iPadOS 18.7.5, or for version 26.x devices install iOS 26.3 or iPadOS 26.3
- For Mac: Open System Settings > General > Software Update and install macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, or macOS Tahoe 26.3 as applicable
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 26.3
- For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 26.3
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26.3
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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-20611 — 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-20611 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