What is the CVSS score of CVE-2026-28943?

CVE-2026-28943 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Apple iOS are affected by CVE-2026-28943?

CVE-2026-28943 affects Apple's operating system family, including iOS, iPadOS, macOS, tvOS, and watchOS, by exposing kernel memory information that bypasses KASLR-a critical security safeguard that…. A patch is available.

How to fix or mitigate CVE-2026-28943?

Within 24 hours: Inventory all Apple devices across the organization (iPhones, iPads, Macs, Apple Watches, Apple TVs) and document current OS versions. Within 7 days: Deploy Apple's security patches for all affected iOS, iPadOS, macOS, tvOS, and watchOS versions through your mobile device management (MDM) or device management platform. Within 30 days: Verify patch deployment across the organization and confirm all devices are running current patched versions.

Apple iOS CVE-2026-28943

EUVD-2026-29252 HIGH

Insertion of Sensitive Information into Log File (CWE-532)

2026-05-11 apple

GHSA-98h5-v6fv-978x

Apple Information Disclosure Ios And Ipados Tvos Watchos

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 08:48 vuln.today

CVSS changed

May 13, 2026 - 16:22 NVD

7.5 (None) 7.5 (HIGH)

Patch available

May 11, 2026 - 22:03 EUVD

CVE Published

May 11, 2026 - 20:07 nvd

HIGH 7.5

CVE Published

May 11, 2026 - 20:07 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

A logging issue was addressed with improved data redaction. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5, tvOS 26.5, watchOS 26.5. An app may be able to determine kernel memory layout.

AnalysisAI

Kernel memory layout disclosure in Apple iOS, iPadOS, macOS, tvOS, and watchOS allows a malicious application to read sensitive log data that exposes kernel address information, enabling KASLR bypass. The flaw stems from insufficient redaction of kernel pointers written to system logs (CWE-532) and was reported and patched by Apple across its operating system families. No public exploit identified at time of analysis and EPSS probability is very low (0.02%), but the issue is typically chained with memory-corruption bugs to achieve reliable kernel exploitation.

Technical ContextAI

The vulnerability is rooted in CWE-532 (Insertion of Sensitive Information into Log File), where Apple's XNU-based kernel or supporting subsystems emitted kernel memory addresses into log output reachable by unprivileged apps. Kernel Address Space Layout Randomization (KASLR) relies on the secrecy of these addresses; once leaked, an attacker can compute the kernel slide and accurately target structures, functions, and gadgets. Per the CPE data, the affected components span Apple's shared codebase across iOS/iPadOS, macOS (Sonoma, Sequoia, Tahoe), tvOS, and watchOS, indicating the leak originates in a cross-platform kernel logging path that Apple addressed by improving data redaction before log emission.

RemediationAI

Apply the vendor-released patches: upgrade to iOS/iPadOS 18.7.9 or 26.5, macOS Sonoma 14.8.7, macOS Sequoia 15.7.7, macOS Tahoe 26.5, tvOS 26.5, or watchOS 26.5 as appropriate for each device, referencing Apple's advisories at support.apple.com/en-us/127110, 127111, 127115, 127116, 127117, 127118, and 127119. No vendor-published workaround exists for kernel log redaction, so compensating controls until patching include restricting App Store and sideloaded application installation via MDM configuration profiles (trade-off: reduces user productivity and blocks legitimate apps), enforcing app vetting and developer-ID restrictions on macOS through Gatekeeper and notarization policies (trade-off: friction for internal tooling), and prioritizing patch deployment on high-risk devices belonging to executives, journalists, and security staff who are realistic targets for chained exploit campaigns.