VulnerabilityPublished 11 May 2026

CVE-2026-28846: Apple iOS and iPadOS · Stack-based Buffer Overflow

Affects Apple iOS and iPadOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 26.5 or 18.7.9 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.5, 18.7.9, 15.7.7 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade iOS and iPadOS to 26.5 or 18.7.9; macOS to 26.5, 15.7.7 or 14.8.7; tvOS and visionOS and watchOS to 26.5.

Affected software

Product	Affected	Fixed in
AppleiOS and iPadOS	Affected <26.5	Fixed in 26.5
AppleiOS and iPadOS	Affected <18.7.9	Fixed in 18.7.9
ApplemacOS	Affected <26.5	Fixed in 26.5
ApplemacOS	Affected <15.7.7	Fixed in 15.7.7
ApplemacOS	Affected <14.8.7	Fixed in 14.8.7
AppletvOS	Affected <26.5	Fixed in 26.5

AI-suggested

Apple has released official fixes for this vulnerability in iOS 18.7.9, iPadOS 18.7.9, and other related OS versions. Users and administrators should apply these updates promptly to remediate the issue. Patch status is confirmed by the vendor advisory. No additional mitigation steps are indicated beyond applying the official updates.

Description

CVE-2026-28846 is a high-severity vulnerability affecting Apple iOS and iPadOS where a buffer overflow issue could allow a remote attacker to cause unexpected app termination. The vulnerability was addressed by Apple through improved bounds checking and fixed in multiple Apple operating system versions including iOS 18.7.9 and iPadOS 18.7.9. The issue does not impact confidentiality or integrity but affects availability by causing application crashes.

Impact

The primary impact is availability disruption due to unexpected application termination caused by a remote attacker exploiting a buffer overflow. There is no impact on confidentiality or integrity according to the CVSS vector. No known exploits have been reported in the wild.

Summary

This vulnerability involves a buffer overflow in Apple iOS and iPadOS that can be triggered remotely to cause unexpected termination of applications. Apple fixed the issue by implementing improved bounds checking in iOS 18.7.9, iPadOS 18.7.9, and corresponding updates for other Apple operating systems. The CVSS score is 7.5 (high), reflecting a network attack vector with no privileges or user interaction required, and impacts availability only (app termination). There is no indication of known exploits in the wild at this time.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
The product writes past the end of a buffer that was allocated on the stack.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 May 2026, 10:53 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats