CVE-2026-28815: Apple macOS · Out-of-bounds Read
Affects Apple macOSSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.1 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 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.
What to do
Upgrade macOS and swift-crypto to 4.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ApplemacOS | Affected
| Fixed in
|
SwiftURLswift-cryptopkg:swift/swift-cryptoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in swift-crypto version 4.3.1. Users and administrators should update to this version to remediate the vulnerability. Since this is not a cloud service, patching the affected software is required. Patch status is confirmed by the vendor advisory indicating the issue is fixed in swift-crypto 4.3.1.
Description
CVE-2026-28815 is a high-severity vulnerability in Apple macOS where a remote attacker can supply a short X-Wing HPKE encapsulated key, triggering an out-of-bounds read in the C decapsulation path. This can cause a crash or potentially disclose memory depending on runtime protections. The issue affects swift-crypto version 4.0.0 and is fixed in version 4.3.1. There are no known exploits in the wild at this time.