CVE-2026-43676 is an out-of-bounds access vulnerability in WebKit affecting Safari and Apple platforms that embed the engine, including affected releases of Safari, iOS, iPadOS, macOS, visionOS, and watchOS. The flaw is triggered when WebKit processes maliciously crafted web content. Apple states the issue was addressed through improved bounds checking. Successful triggering leads to an unexpected Safari or related web-content process crash, indicating a memory-safety error in WebKit’s handling of attacker-controlled content.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A WebKit vulnerability in Apple platforms where malicious web content may cause Safari to crash unexpectedly.
A WebKit vulnerability where processing maliciously crafted web content may lead to an unexpected Safari crash.
An out-of-bounds access vulnerability in web content processing that could cause an unexpected Safari crash.
A macOS Tahoe web content processing vulnerability involving out-of-bounds access that may cause an unexpected Safari crash.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.