CVE-2026-28819
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 bounds checking. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5. An app may be able to execute arbitrary code with kernel privileges.
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's kernel allows a malicious application to execute arbitrary code with kernel-level privileges due to insufficient bounds checking. This represents a privilege escalation vulnerability affecting multiple Apple operating system versions.
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< 18.7.9>= 14.0, < 14.8.7>= 15.0, < 15.7.7>= 26.0, < 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 version on iPhoneGo to Settings > General > About > Version, or use Apple Configurator, Finder, or Xcode to check the iOS versionAffected if version is less than 18.7.9 (any version below 18.7.9 is affected)
-
Check iPadOS version on iPadGo to Settings > General > About > Version, or use Apple Configurator, Finder, or Xcode to check the iPadOS versionAffected if version is less than 18.7.9 (any version below 18.7.9 is affected)
-
Check macOS version on MacRun `sw_vers -ProductVersion` in Terminal, or open System Settings > About > macOSAffected if version is 14.0 through 14.8.6, 15.0 through 15.7.6, or 26.0 through 26.4 (any version in these ranges is affected)
A device is affected if it runs iOS/iPadOS below 18.7.9 or macOS 14.0-14.8.6, 15.0-15.7.6, or 26.0-26.4, as the kernel bounds checking vulnerability exists in all these versions.
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
Update affected devices to iOS 18.7.9, iPadOS 18.7.9, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, or macOS Tahoe 26.5 or later to apply the bounds checking fix.
iOS 18.7.9/iPadOS 18.7.9; macOS Sonoma 14.8.7; macOS Sequoia 15.7.7; macOS Tahoe 26.5
- 1. Back up your device data before performing any system update.
- 2. For iOS/iPadOS devices: Go to Settings > General > Software Update and install iOS 18.7.9 or iPadOS 18.7.9.
- 3. For macOS devices: Open System Settings > General > Software Update and install the appropriate security update: macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, or macOS Tahoe 26.5.
- 4. After updating, verify the installed version matches the required security patch level.
- 5. Restart the device if prompted to complete the installation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28819 — 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-28819 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