CVE-2026-28852
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 stack overflow was addressed with improved input validation. This issue is fixed in iOS 18.7.7 and iPadOS 18.7.7, iOS 26.4 and iPadOS 26.4, macOS Sequoia 15.7.5, macOS Tahoe 26.4, tvOS 26.4, visionOS 26.4, watchOS 26.4. An app may be able to cause a denial-of-service.
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 confidenceA stack overflow vulnerability in Apple's operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows a malicious application to trigger excessive stack allocation, leading to a denial-of-service condition. The vulnerability was addressed through improved input validation.
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.7>= 26.0, < 26.4< 18.7.7>= 26.0, < 26.4>= 15.0, < 15.7.5>= 26.0, < 26.4< 26.4< 26.4< 26.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 operating system and versionOn iOS/iPadOS: go to Settings > General > About; on macOS: go to System Settings > General > About; on tvOS/watchOS/visionOS: go to Settings > General > About. Note the version number displayed.Affected if Unable to determine the OS version from system settings
-
Check iOS or iPadOS version against affected rangesIf running iOS or iPadOS, compare your version number to: any version below 18.7.7, or any version from 26.0 up to (but not including) 26.4. These ranges are vulnerable.Affected if Your iOS version is < 18.7.7 OR (>= 26.0 AND < 26.4), or your iPadOS version is < 18.7.7 OR (>= 26.0 AND < 26.4)
-
Check macOS version against affected rangesIf running macOS, compare your version to: any version from 15.0 up to (but not including) 15.7.5, or any version from 26.0 up to (but not including) 26.4. These ranges are vulnerable.Affected if Your macOS version is >= 15.0 AND < 15.7.5, OR >= 26.0 AND < 26.4
-
Check tvOS, visionOS, or watchOS version against affected rangesIf running tvOS, visionOS, or watchOS, compare your version to any version below 26.4. All versions prior to 26.4 are vulnerable.Affected if Your tvOS version is < 26.4, your visionOS version is < 26.4, or your watchOS version is < 26.4
You are affected if your Apple OS version matches any of the vulnerable ranges: iOS/iPadOS < 18.7.7 or 26.0-26.3, macOS 15.0-15.7.4 or 26.0-26.3, or any tvOS/visionOS/watchOS version below 26.4.
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 · scoped15.7.518.7.726.4
Apply the vendor-supplied security updates: iOS 18.7.7 and iOS 26.4+, iPadOS 18.7.7 and iPadOS 26.4+, macOS Sequoia 15.7.5 and macOS Tahoe 26.4+, tvOS 26.4, visionOS 26.4, watchOS 26.4.
iOS 18.7.7 and iPadOS 18.7.7 (for <18.7.7); iOS 26.4 and iPadOS 26.4 (for >=26.0,<26.4); macOS Sequoia 15.7.5 (for >=15.0,<15.7.5); macOS Tahoe 26.4 (for >=26.0,<26.4); tvOS 26.4; visionOS 26.4; watchOS 26.4
- Check the current version of the affected Apple device (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- On iPhone/iPad: Go to Settings > General > Software Update to check for and install the update
- On Mac: Go to System Settings > General > Software Update to check for and install the update
- On Apple TV: Go to Settings > System > Software Updates > Update Software
- On Apple Watch: On the connected iPhone, open the Watch app and go to General > Software Update
- On Apple Vision Pro: Go to Settings > General > Software Update
- Apply the appropriate update: iOS/iPadOS 18.7.7, iOS/iPadOS 26.4, macOS Sequoia 15.7.5, macOS Tahoe 26.4, tvOS 26.4, visionOS 26.4, or watchOS 26.4 depending on your device and current version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28852 — 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-28852 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