8 matches found
CVE-2026-43734
A use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. Processing maliciously crafted web content may lead to an unexpected process crash...
CVE-2026-43745
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. Processing maliciously crafted web content may lead to an unexpected Safari crash...
CVE-2026-43709
A use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. Processing maliciously crafted web content may lead to an unexpected process crash...
CVE-2026-43705
A type confusion issue was addressed with improved checks. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. Processing maliciously crafted web content may lead to memory corruption...
CVE-2026-43700
CVE-2026-43700 describes a cross-origin issue in WebKit/Safari where processing maliciously crafted web content could disclose sensitive user information. The record states the root cause as improper tracking of security origins and the fix shipped in Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, and...
CVE-2026-43699
CVE-2026-43699 is a use-after-free vulnerability in WebKit-related components that could be triggered by processing malicious web content, potentially causing an unexpected process crash. The issue is addressed with memory-management fixes and is fixed in Safari 26.5.2, iOS 26.5.2 / iPadOS 26.5.2...
CVE-2026-43725
The issue was addressed with improved input validation. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. A malicious website may be able to process restricted web content outside the sandbox...
CVE-2026-43715
CVE-2026-43715 is a use-after-free vulnerability in WebKit components affecting Safari, iOS, iPadOS, and macOS Tahoe. The issue arises from memory mismanagement that may lead to memory corruption when processing malicious web content. It is fixed in Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, and m...