Quick answers
- Is CVE-2026-112666 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112666 being exploited in the wild.
- How severe is CVE-2026-112666?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Apple Safari before 27.2.
- Is there a fix for CVE-2026-112666?
- Yes: fixed in Safari 27.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112666 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112666?
- Check whether you run Apple Safari at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Safari 27.2
Technical details
A use-after-free vulnerability in Safari's WebKit engine allows an attacker to trigger unexpected process termination by processing maliciously crafted web content. The vulnerability requires network-based delivery of the malicious content (user visits a compromised or attacker-controlled website). The fix involves improved memory management to prevent the memory from being accessed after it has been freed.
Affected products
- Apple Safari before 27.2
Timeline
- 2026-10-26: disclosed