Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds write in Apple kernel components / process crash in WebRTC

IdentifiersCVE-2026-28944CWE-787

CVE-2026-28944 is inconsistently described across the provided Apple advisory excerpts. Multiple Safari/WebRTC and visionOS/macOS Sonoma/macOS Sequoia contexts describe it as a WebRTC issue where processing maliciously crafted web content may lead to an unexpected process crash, fixed with improved memory handling and associated with WebKit Bugzilla 311131. Separately, macOS Tahoe and some broader Apple platform summaries describe CVE-2026-28944 as an out-of-bounds write issue that could allow an app to execute arbitrary code with kernel privileges. Based on the more specific vulnerability-type attribution in the supplied material, the strongest CWE mapping is CWE-787 (out-of-bounds write), but the record should be treated cautiously because the source content contains conflicting product/component descriptions for the same CVE.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Based on the supplied content, successful exploitation can result in at least denial of service via unexpected process crash when malicious web content is processed. In some provided Apple advisory summaries for macOS Tahoe, the same CVE is described as enabling arbitrary code execution with kernel privileges, which would represent full system compromise. Because the provided sources conflict, the minimum verified impact is process crash/DoS; higher-impact kernel-level code execution is reported in some excerpts but cannot be stated with full confidence without authoritative single-source confirmation.

Mitigation

If you can’t patch tonight, do this now.

Until patches are applied, reduce exposure to untrusted web content and limit use of Safari/WebRTC-capable applications on affected systems. Enterprise mitigations may include restricting browsing to trusted sites, disabling or limiting WebRTC where operationally feasible, and isolating high-risk browsing activity. If the kernel-level Tahoe description is accurate for some affected configurations, standard hardening measures such as minimizing local app execution from untrusted sources are also relevant. No complete workaround is provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply the vendor fixes referenced in the provided content: Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, and visionOS 26.5, as applicable to the affected platform. The issue was addressed by Apple with improved memory handling in the WebRTC/web-content contexts; some Tahoe summaries also reference improved bounds checking for an out-of-bounds write variant. Use the latest Apple security updates for the relevant OS/browser branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIosoperating_system
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
AppleMacos Tahoeoperating_system
AppleVisionosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.