CVE-2026-28868: A logging issue was addressed with improved data redaction.
A logging issue was addressed with improved data redaction. This issue is fixed in iOS 18.7.7 and iPadOS 18.7.7, iOS 26.4 and iPadOS 26.4, macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.4, visionOS 26.4, watchOS 26.4. An app may be able to disclose kernel memory.
Security readout for executives and security teams
Plain-English summary
A flaw in Apple operating-system logging could let an app expose kernel memory, potentially revealing sensitive data. The issue affects confidentiality only; the supplied evidence does not indicate data modification, service disruption, or remote exploitation. Apple addressed it through improved log redaction in specified operating-system updates.
Executive priority
Schedule prompt remediation through normal patch governance, prioritizing higher-risk endpoints and devices exposed to untrusted apps. The confidentiality impact can be significant, but available evidence supports moderate urgency rather than emergency response because exploitation is unconfirmed and local user interaction is required.
Technical view
CVE-2026-28868 is a CWE-532 information-disclosure issue involving insufficient redaction of logged data. The CVSS 3.1 score is 5.5: local access, low complexity, no privileges, and user interaction, with high confidentiality impact. Apple states that an app may disclose kernel memory. Exact vulnerable version ranges are not provided.
Likely exposure
Potentially exposed assets are Apple devices running releases earlier than the named fixes: iOS/iPadOS 18.7.7 or 26.4, macOS Sequoia 15.7.5, Sonoma 14.8.5, Tahoe 26.4, visionOS 26.4, and watchOS 26.4. The source bundle does not define precise lower affected-version boundaries.
Exploitation context
The supplied CVSS vector indicates a local attack requiring user interaction but no prior privileges. The issue is not listed as KEV in the bundle, and no cited source establishes active exploitation or public exploit availability. Treat exploitation status as unconfirmed.
Researcher notes
The flaw concerns sensitive information written to logs without adequate redaction. Apple describes the possible result only as kernel-memory disclosure and provides no additional trigger, component, or affected-range detail in the supplied bundle. Validation should remain version-based; deeper exploitability conclusions would require evidence not provided here.
Mitigation direction
Update affected Apple devices to the listed fixed release or a later supported release.
Prioritize devices that install or execute untrusted applications.
Use device-management controls to enforce minimum operating-system versions.
Check Apple security guidance for any later remediation details.
Validation and detection
Inventory iOS, iPadOS, macOS, visionOS, and watchOS versions across managed assets.
Confirm each device meets the applicable fixed-version threshold.
Review device-management compliance reports for outdated or unmanaged devices.
Verify update deployment completed successfully on representative devices.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-532 · source CWE mapping
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.