Apple iOS vulnerabilities in 2026: Coruna, DarkSword and MoldyRoost (not a breach)
Apple's iPhones are a prime target for exploit kits because one working chain reaches messages, keychains and crypto wallets. This page tracks exploited Apple vulnerabilities we have covered and the campaigns using them, and keeps them apart from any claim of a breach at Apple.
Short answer
Was Apple hacked?
No breach of Apple is reported in the sources we read; CVE-2023-43000 is a vulnerability in Apple software, not a breach of Apple. It is a WebKit use-after-free that Apple fixed in iOS 16.6 in July 2023 and backported in iOS 15.8.7 in March 2026, linking it to the Coruna exploit. CISA has listed it as known exploited since 5 March 2026.
On 20 November 2026 Confiant reported that a malvertising operation it calls MoldyRoost used more than 480 ad domains to deliver the Coruna, DarkSword, GhostWave and SilkPath kits to older iPhones, and matched Coruna's first stage to CVE-2023-43000. Confiant reports no victim count and no Apple statement.
Timeline at a glance
24 Jul 2023Apple fixes WebKit use-after-free CVE-2023-43000 in iOS 16.6 (CVE entry added to the notes 11 Nov 2025). (Apple)Not a breach
5 Mar 2026CISA adds CVE-2023-43000 to KEV. (CISA)Confirmed
11 Mar 2026Apple backports the fix in iOS 15.8.7, linking it to the Coruna exploit. (Apple)Not a breach
20 Nov 2026Confiant reports MoldyRoost malvertising delivering Coruna and DarkSword to older iPhones via 480+ ad domains. (Confiant)Reported
Last updated 22 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
Apple incident timeline, in detail
Confirmed = acknowledged by Apple, a regulator filing or a court. Reported = credible reporting Apple has not fully confirmed. Unverified claim = an attacker or leak-site claim.
May-Nov 2026Not a breachExploited product vulnerabilities (iOS WebKit and kernel chains)
What happened. Confiant says MoldyRoost bought programmatic ads, cloaked landing pages by device and routed iPhones by iOS version to four kits: Coruna (iOS 13.0 to 17.2.1), DarkSword (18.4 to 18.7), GhostWave (up-to-date iOS 18, branch for 26.3) and SilkPath. It names one CVE: CVE-2023-43000, a WebKit use-after-free Apple fixed in iOS 16.6 and iOS 15.8.7.
Impact. Per Confiant, payloads target crypto wallets and seed phrases, the keychain, iMessage, WhatsApp and Telegram data, photos and location. Confiant says Apple had fixed all six DarkSword bugs by iOS 26.3 (citing Google's threat intelligence group) and that it saw no iOS 26 exploit code. No victim count and no Apple statement are reported.
Dates: Apple shipped the CVE-2023-43000 fix on 24 July 2023 but only added the CVE to its release notes on 11 November 2025; the CVE was published on 5 November 2025.
Coverage: Confiant names CVE-2023-43000 only; the CVEs for DarkSword, GhostWave and SilkPath are not named in the sources we read.
The pattern across the record
Old iOS versions stay a target
Every kit Confiant describes aims at releases Apple has already fixed, so the update gap on staff phones is the exposure.
Vulnerabilities are not breaches
Nothing reported shows an intrusion at Apple. The risk is to iPhones that are not on a current iOS release.
What it means for Apple customers — and what to do
If your staff use iPhones, the question is how many run an old iOS release and who holds wallets or sensitive data on a phone.
1.Enforce a minimum iOS version
Use MDM to require the current iOS release before phones reach mail and SSO.
No breach of Apple is reported. CVE-2023-43000 and the flaws behind the Coruna and DarkSword kits are vulnerabilities in Apple software, used against iPhones that are not up to date.
What is CVE-2023-43000?+
A WebKit use-after-free that Apple fixed in iOS 16.6 (July 2023) and iOS 15.8.7 (March 2026). Crafted web content can cause memory corruption. CISA lists it as known exploited since 5 March 2026, and Confiant ties it to the Coruna kit used by MoldyRoost.
Does MoldyRoost work on current iPhones?+
Confiant says the kits target older iOS versions and that it saw no iOS 26 exploit code. Keeping iPhones on the current iOS release is the main defence.
More in the Breach Index
Same sourced, verification-tagged timeline, company by company — compare how peers have fared.
Independent analysis for security-leadership education; not affiliated with or endorsed by Apple. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.