CVE-2026-28972
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 write issue was addressed with improved input validation. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5. An app may be able to cause unexpected system termination or write kernel 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 confidenceAn out-of-bounds write vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) that was addressed through improved input validation. A malicious application could exploit this to cause unexpected system termination or write to kernel memory, potentially leading to privilege escalation.
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.9>= 26.0, < 26.5< 18.7.9>= 26.0, < 26.5>= 14.0, < 14.8.7>= 15.0, < 15.7.7>= 26.0, < 26.5< 26.5< 26.5< 26.5CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 and note the iOS version numberAffected if Version is less than 18.7.9, or >= 26.0 and less than 26.5
-
Check iPadOS version on iPadGo to Settings > General > About and note the iPadOS version numberAffected if Version is less than 18.7.9, or >= 26.0 and less than 26.5
-
Check macOS version on MacClick Apple menu > About This Mac and note the macOS version numberAffected if Version is >= 14.0 and less than 14.8.7, or >= 15.0 and less than 15.7.7, or >= 26.0 and less than 26.5
-
Check tvOS version on Apple TVGo to Settings > General > About and note the tvOS version numberAffected if Version is less than 26.5
-
Check visionOS version on Apple Vision ProGo to Settings > General > About and note the visionOS version numberAffected if Version is less than 26.5
-
Check watchOS version on Apple WatchOn iPhone, open Watch app > My Watch > General > About and note the watchOS version numberAffected if Version is less than 26.5
Your device is affected if the installed OS version falls within any of the vulnerable ranges: below 18.7.9 (for iOS/iPadOS 18.x), between 26.0-26.4, or below the patched version for tvOS/visionOS/watchOS.
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.715.7.718.7.9
Apply the available security updates: iOS 18.7.9/iOS 26.5 and iPadOS 18.7.9/iPadOS 26.5, macOS Sequoia 15.7.7/macOS Sonoma 14.8.7/macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, and watchOS 26.5.
iOS 18.7.9/iPadOS 18.7.9 or iOS 26.5/iPadOS 26.5; macOS Sonoma 14.8.7 or macOS Sequoia 15.7.7 or macOS Tahoe 26.5; tvOS 26.5; visionOS 26.5; watchOS 26.5
- Check current device version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
- Ensure device is connected to Wi-Fi and has sufficient battery or is plugged into power
- On iOS/iPadOS: Go to Settings > General > Software Update and download/install the latest update
- On macOS: Go to System Settings > General > Software Update and download/install the latest update
- On tvOS: Go to Settings > System > Software Updates and enable "Update Software"
- On watchOS: On iPhone, open Watch app, go to General > Software Update
- On visionOS: Go to Settings > General > Software Update
- After update completes, verify the version matches the fixed release (18.7.9, 26.5, 14.8.7, 15.7.7, or 26.5 depending on your device)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28972 — 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-28972 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