Sensitive-data disclosure via improper path validation
Published May 13, 2024 · Updated Apr 2, 2026
Path traversal in Apple Shortcuts before iOS and iPadOS 17.5, macOS Sonoma 14.5, and watchOS 10.5 allows attackers to expose sensitive user data. Apple identifies the locus only as path handling in Shortcuts and has not published the affected function or exact path operation that bypasses consent. The shortcut must reach the flawed path-handling flow; the documented consequence is unauthorized disclosure, not data modification or service interruption.
Summary
What happened
Path traversal in Apple Shortcuts before iOS and iPadOS 17.5, macOS Sonoma 14.5, and watchOS 10.5 allows attackers to expose sensitive user data. Apple identifies the locus only as path handling in Shortcuts and has not published the affected function or exact path operation that bypasses consent. The shortcut must reach the flawed path-handling flow; the documented consequence is unauthorized disclosure, not data modification or service interruption.
The record
- CVE
- CVE-2024-27821
- Published
- May 13, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <17.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WorkflowKit extraction and signing race PoCsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo