CVE-2026-28846
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 buffer overflow was addressed with improved bounds checking. 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. A remote attacker may be able to cause unexpected app termination.
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 confidenceBuffer overflow vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allowing remote attackers to cause unexpected app termination via memory corruption.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify your Apple device operating systemDetermine whether the device runs iOS, iPadOS, macOS, tvOS, visionOS, or watchOS. This vulnerability affects all these Apple operating systems.Affected if The device runs any of these Apple operating systems.
-
Check iOS or iPadOS versionOpen Settings > General > About and note the version number displayed (for example, 18.7.1 or 26.4).Affected if The installed version is less than 18.7.9, OR is 26.0 or higher but less than 26.5.
-
Check macOS versionClick the Apple menu > About This Mac. Note the version number (for example, 14.6.1, 15.5, or 26.4).Affected if The installed version is 14.0 or higher but less than 14.8.7, OR is 15.0 or higher but less than 15.7.7, OR is 26.0 or higher but less than 26.5.
-
Check tvOS, visionOS, or watchOS versionOpen Settings > General > About on the Apple TV, Vision Pro, or Apple Watch. Note the version number.Affected if The installed version is lower than 26.5.
You are affected if your device runs any of the listed Apple operating systems and its current version falls within the specific vulnerable ranges shown 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.715.7.718.7.9
Apply the relevant security updates (iOS 18.7.9/26.5, iPadOS 18.7.9/26.5, macOS 15.7.7/14.8.7/26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5) to affected devices.
iOS 18.7.9 / iPadOS 18.7.9 / iOS 26.5 / iPadOS 26.5 / macOS Sonoma 14.8.7 / macOS Sequoia 15.7.7 / macOS Tahoe 26.5 / tvOS 26.5 / visionOS 26.5 / watchOS 26.5 (depending on device and current version)
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- Check the current OS version installed on the device
- For iPhone/iPad: If running iOS/iPadOS < 18.7.9, upgrade to iOS 18.7.9 or iPadOS 18.7.9; if running >= 26.0 and < 26.5, upgrade to iOS 26.5 or iPadOS 26.5
- For Mac: If running macOS Sonoma (14.x) < 14.8.7, upgrade to macOS Sonoma 14.8.7; if running macOS Sequoia (15.x) < 15.7.7, upgrade to macOS Sequoia 15.7.7; if running macOS Tahoe (26.x) < 26.5, upgrade to macOS Tahoe 26.5
- For Apple TV: Upgrade to tvOS 26.5
- For Apple Vision Pro: Upgrade to visionOS 26.5
- For Apple Watch: Upgrade to watchOS 26.5
- Perform the upgrade via Settings > General > Software Update (iOS/iPadOS/watchOS/tvOS/visionOS) or System Settings > Software Update (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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-28846 — 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-28846 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