CVE-2026-20682
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 state management. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3. An attacker may be able to discover a user’s deleted notes.
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 iOS and iPadOS allows an attacker to access notes that a user has deleted. The vulnerability stems from improper state management in the Notes application, where deleted notes remain discoverable through some interface or API rather than being properly purged from accessible storage.
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.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the iOS or iPadOS version installed on the deviceGo to Settings > General > About on the iPhone or iPad and note the version number displayed next to 'Version'Affected if The installed version is less than 18.7.5, or is 26.0 through 26.2 (any version in the range >= 26.0 and < 26.3)
-
Confirm the device is an iPhone or iPadVerify the device model through Settings > General > About > Model NameAffected if The device is an Apple iPhone or iPad running a vulnerable iOS/iPadOS version from step 1
-
Understand the vulnerability scopeThis flaw exists in the Notes application state management on vulnerable iOS/iPadOS versions - deleted notes may remain discoverable through some interface or API rather than being properly purgedAffected if The device runs a vulnerable iOS/iPadOS version and the Notes app contains or previously contained deleted notes that should have been purged
The device is affected if it runs iOS/iPadOS versions less than 18.7.5, or versions 26.0 through 26.2, on an iPhone or iPad.
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 · scoped18.7.526.3
Update affected iOS devices to iOS 18.7.5/iPadOS 18.7.5 or iOS 26.3/iPadOS 26.3 to patch the logic error in state management.
iOS 18.7.5 / iPadOS 18.7.5 or iOS 26.3 / iPadOS 26.3
- Back up your device data using iCloud or iTunes/Finder before upgrading
- Connect your device to Wi-Fi and power
- Go to Settings > General > Software Update
- Download and install the available update (iOS 18.7.5 or iOS 26.3 / iPadOS 18.7.5 or iPadOS 26.3)
- Ensure the update completes successfully and verify the new iOS version in Settings > General > About
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-20682 — 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-20682 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