CVE-2026-20673
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 · uneditedA logic issue was addressed with improved checks. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3. Turning off "Load remote content in messages” may not apply to all mail previews.
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 logic flaw in Apple Mail prevented the 'Load remote content in messages' privacy setting from applying consistently across all mail previews. Remote content (images, tracking pixels) could still load in certain preview scenarios even when users explicitly disabled this feature, allowing email senders to potentially track email opens and capture user IP addresses.
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< 18.7.5< 14.8.4>= 15.0, < 15.7.4>= 26.0, < 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 iPhone or iPad. Note the version number shown.Affected if Version is earlier than 18.7.5 on iPhone or iPadOS.
-
Check macOS versionClick Apple menu > About This Mac. Note the version number shown.Affected if Version is earlier than 14.8.4, or between 15.0 and 15.7.3, or between 26.0 and 26.2.
-
Locate Apple Mail privacy settingOn iPhone/iPad: Go to Settings > Mail > Privacy Protection. On macOS: Open Mail, go to Mail > Settings > Privacy. Find the 'Load remote content in messages' toggle.Affected if The toggle exists and can be inspected.
-
Confirm affected configurationIf using an affected OS version (steps 1-2) and the 'Load remote content in messages' setting is disabled, the environment is vulnerable to remote content loading in mail previews despite the setting.Affected if OS version is in the affected range AND the privacy setting to block remote content is disabled (or was disabled during use).
The environment is affected if the device runs an iOS/iPadOS version before 18.7.5 or a macOS version before 14.8.4 (or in the 15.0-15.7.3 or 26.0-26.2 ranges), and the user relies on Apple Mail's privacy setting to block remote content in emails.
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 vendor-supplied updates: iOS 18.7.5, iPadOS 18.7.5, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, or macOS Tahoe 26.3 depending on the affected device.
iOS 18.7.5 / iPadOS 18.7.5 / macOS Sonoma 14.8.4 / macOS Sequoia 15.7.4 / macOS Tahoe 26.3
- Check current iOS version: Go to Settings > General > About on iPhone or iPad
- Check current iPadOS version: Go to Settings > General > About on iPad
- Check current macOS version: Click Apple menu > About This Mac
- For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS 18.7.5 or iPadOS 18.7.5
- For macOS Sonoma (14.x): Go to System Settings > General > Software Update and upgrade to 14.8.4
- For macOS Sequoia (15.x): Go to System Settings > General > Software Update and upgrade to 15.7.4
- For macOS Tahoe (26.x): Go to System Settings > General > Software Update and upgrade to 26.3
- After update, verify the fix by confirming that 'Load remote content in messages' setting is properly applied to all mail previews
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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-20673 — 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-20673 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