Cyber Resilience

CVE-2026-43717

Memory Safety in Apple Safari ≤ 26.5.2

Memory Safety
Published
29 June 2026
Modified
27 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0022 13th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-43717 is a medium-severity Use After Free (CWE-416) vulnerability in Apple Safari. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-16 (Memory Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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, tvOS 26.6, watchOS 26.6. Processing maliciously crafted web content may lead to an unexpected Safari crash.

CWE(s)
CWE-416

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-43368Same product: Apple Ipados
CVE-2026-43742Same product: Apple Ipados
CVE-2025-43536Same product: Apple Ipados
CVE-2026-43715Same product: Apple Ipados
CVE-2026-43746Same product: Apple Ipados
CVE-2026-43734Same product: Apple Ipados
CVE-2022-22620Same product: Apple Ipados
CVE-2023-28205Same product: Apple Ipados
CVE-2026-43720Same product: Apple Ipados
CVE-2026-43726Same product: Apple Ipados

Affected Assets

apple
safari
≤ 26.5.2
apple
ipados
≤ 26.5.2
apple
iphone os
≤ 26.5.2
apple
macos
26.0 — 26.5.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-16 Memory Protection
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Mitigating Controls (NIST 800-53 r5) AI

SI-16 Memory Protection good match
prevent

Directly enforces memory protection mechanisms that prevent use-after-free conditions during web content processing.

SI-10 Information Input Validation partial match
prevent

Requires validation of untrusted web content inputs that trigger the memory corruption in the browser engine.

SI-7 Software, Firmware, and Information Integrity partial match
detect

Verifies integrity of executing browser code and data structures to identify corruption from the use-after-free flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

References