CVE-2026-20688

Apple macOS path traversal

9.3 CRITICALEPSS 0.27%

Published25 Mar 2026

Description

A path handling issue was addressed with improved validation. This issue is fixed in iOS 26.4 and iPadOS 26.4, macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.4, visionOS 26.4. An app may be able to break out of its sandbox.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Apple iPadOS< 26.4

Apple iPhone OS< 26.4

Apple macOS≥ 14.0 < 14.8.5 · ≥ 15.0 < 15.7.5 · ≥ 26.0 < 26.4

Apple Visionos< 26.4

Remediation

Fixed in

Apple iPadOS≥ 26.4

Apple iPhone OS≥ 26.4

Apple macOS≥ 14.8.5

Apple Visionos≥ 26.4

Patch & vendor advisories

References

https://support.apple.com/en-us/126792Release NotesVendor Advisory
https://support.apple.com/en-us/126794Release NotesVendor Advisory
https://support.apple.com/en-us/126795Release NotesVendor Advisory
https://support.apple.com/en-us/126796Release NotesVendor Advisory
https://support.apple.com/en-us/126799Release NotesVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-20688 being actively exploited?

CVE-2026-20688 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.27%.

How severe is CVE-2026-20688?

CVE-2026-20688 has a CVSS 3.1 base score of 9.3, rated critical. EPSS estimates a 0.27% probability of exploitation.

Which products are affected by CVE-2026-20688?

Affected products include Apple iPadOS, Apple iPhone OS, Apple macOS, Apple Visionos.

How do I fix CVE-2026-20688?

Upgrade affected software to a fixed version, for example Apple iPadOS 26.4, Apple iPhone OS 26.4, Apple macOS 14.8.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-20688 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.