CVE-2026-20634
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 · uneditedThe issue was addressed with improved memory handling. 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 image may result in disclosure of 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 · high confidenceThis is a memory handling vulnerability in Apple's core media processing components. When a device processes a maliciously crafted image file, it can lead to disclosure of process memory contents. The vulnerability is triggered simply by the device processing the crafted image, making it easily exploitable.
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.0, < 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 iOS or iPadOS versionGo to Settings > General > About on the device and note the version number (for example, 18.4 or 26.1)Affected if The version is below 18.7.5, or falls between 26.0 and 26.3 (including 26.0, 26.1, or 26.2)
-
Check macOS versionClick the Apple menu > About This Mac and note the version number (for example, 14.5 or 15.4)Affected if The version is 14.0 or higher but below 14.8.4, OR 15.0 or higher but below 15.7.4, OR 26.0 or higher but below 26.3
-
Check tvOS, visionOS, or watchOS versionOn Apple TV, go to Settings > General > About > Version. On Apple Watch, open the Watch app on iPhone and go to General > About. On Apple Vision Pro, go to Settings > General > About.Affected if The version is below 26.3 (for example, 26.0, 26.1, or 26.2)
If your device runs any of the listed Apple operating systems and its version falls within the vulnerable ranges, your device is affected by this memory disclosure vulnerability when processing image files.
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 available Apple updates: iOS 18.7.5/iPadOS 18.7.5 or iOS 26.3/iPadOS 26.3, macOS Sequoia 15.7.4/Sonoma 14.8.4/Tahoe 26.3, tvOS 26.3, visionOS 26.3, or watchOS 26.3 depending on the affected device.
iOS 18.7.5/iPadOS 18.7.5 or iOS 26.3/iPadOS 26.3 for mobile devices; macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, or macOS Tahoe 26.3 for Macs; tvOS 26.3, visionOS 26.3, or watchOS 26.3 for respective devices
- 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/watchOS/visionOS) or System Settings > General > About (macOS)
- For iPhone/iPad: Go to Settings > General > Software Update and install the available update to reach iOS 18.7.5/iPadOS 18.7.5 or iOS 26.3/iPadOS 26.3
- For Mac: Go to System Settings > General > Software Update and install the available update to reach macOS 14.8.4 (Sonoma), 15.7.4 (Sequoia), or 26.3 (Tahoe)
- For Apple TV: Go to Settings > System > Software Updates and update to tvOS 26.3
- For Apple Vision Pro: Go to Settings > General > Software Update and update to visionOS 26.3
- For Apple Watch: Go to Settings > General > Software Update on the watch or through the paired iPhone, and update to watchOS 26.3
- Verify the update was successful by checking Settings > General > About to confirm the installed OS version matches the target fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20634 — 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-20634 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