CVE-2026-20675
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 bounds checks. 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 lead to disclosure of user information.
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 confidenceA bounds checking vulnerability in image processing components allows a maliciously crafted image to trigger an out-of-bounds read, potentially exposing sensitive user information. The fix implements proper boundary validation during image parsing operations.
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 version on iPhoneGo to Settings > General > About > Software Version or run 'sw_vers' in Terminal on macOS if the iPhone is connectedAffected if Version is below 18.7.5 OR between 26.0 and 26.2 (exclusive of 26.3)
-
Check iPadOS version on iPadGo to Settings > General > About > Software Version or run 'sw_vers' in Terminal on macOS if the iPad is connectedAffected if Version is below 18.7.5 OR between 26.0 and 26.2 (exclusive of 26.3)
-
Check macOS version on MacGo to System Settings > About or run 'sw_vers' in TerminalAffected if Version is 14.0 to 14.8.3, 15.0 to 15.7.3, or 26.0 to 26.2 (exclusive of 26.3)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version or use the Remote: Settings > General > AboutAffected if Version is below 26.3 (any version starting from initial release up to 26.2)
-
Check visionOS version on Apple Vision ProGo to Settings > General > About > Software VersionAffected if Version is below 26.3 (any version up to 26.2)
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone > General > About, or go to Settings > General > About on the Watch itselfAffected if Version is below 26.3 (any version up to 26.2)
You are affected if your device runs any iOS, iPadOS, macOS, tvOS, visionOS, or watchOS version that falls within the ranges listed as vulnerable for that product.
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 security 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, watchOS 26.3) to affected devices to remediate this vulnerability.
iOS 18.7.5/iPadOS 18.7.5 (older devices) or iOS 26.3/iPadOS 26.3 (newer devices); macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, or macOS Tahoe 26.3; tvOS 26.3; watchOS 26.3; visionOS 26.3
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18.7.5 or iPadOS 18.7.5 (for older devices)
- For iPhone/iPad on modern versions: Go to Settings > General > Software Update and 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
- After updating, verify the update was successful by checking the OS version in Settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20675 — 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-20675 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