CVE-2026-28875
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 26.4 and iPadOS 26.4. A remote attacker 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 buffer overflow vulnerability in iOS 26.4 and iPadOS 26.4 allows a remote attacker to cause denial-of-service. The issue was addressed through improved bounds checking, indicating the vulnerability involved improper memory handling when processing incoming data.
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< 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
- 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.
-
Check iOS version on iPhoneOn the iPhone, go to Settings > General > About and read the Version fieldAffected if The version number is less than 26.4 (for example, 26.3, 26.2, etc.)
-
Check iPadOS version on iPadOn the iPad, go to Settings > General > About and read the Version fieldAffected if The version number is less than 26.4 (for example, 26.3, 26.2, etc.)
-
Identify device model and OS familyCheck if the device is an iPhone (iOS) or iPad (iPadOS) in Settings > General > About > Model NameAffected if The device is an iPhone or iPad running any version below 26.4
A user is affected if their iPhone runs iOS below 26.4 or their iPad runs iPadOS below 26.4, regardless of network configuration, since the vulnerability is triggered by processing incoming data.
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 · scoped26.4
Apply iOS 26.4 and iPadOS 26.4 security updates to all affected devices. Organizations should deploy via MDM and verify completion.
iOS 26.4 and iPadOS 26.4
- Back up your device data using iCloud or Finder/iTunes before upgrading
- Connect your device to Wi-Fi and ensure sufficient battery charge (or connect to power)
- Go to Settings > General > Software Update
- Download and install iOS 26.4 (iPhone) or iPadOS 26.4 (iPad)
- Restart the device after the update completes
- Verify the update by checking Settings > General > About > Software Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28875 — 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-28875 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