# CVE-2024-27821: Path traversal in iOS and iPadOS

> A path handling flaw in Apple operating systems allows shortcuts to output sensitive user data without consent.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2024
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-69wv-v57r-pj37

## What is CVE-2024-27821?

CVE-2024-27821 is a high-severity path traversal vulnerability in Apple Ipados, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path handling issue was addressed with improved validation. This issue is fixed in iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, watchOS 10.5. A shortcut may output sensitive user data without consent.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-27821?

It affects 4 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Watchos.

## How do I fix CVE-2024-27821?

No fix has been published for CVE-2024-27821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-27821 being exploited?

There is no known exploitation of CVE-2024-27821 in the wild and no public exploit code.

Public exploit code:

- Writeup and PoC of CVE-2024-27821, for education purposes. (github_poc): https://github.com/0xilis/CVE-2024-27821

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27821 and fix it if it is affected.

What it is: CVE-2024-27821 is a high-severity path traversal vulnerability in Apple Ipados, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27821 in the wild and no public exploit code.

Affected product: Apple Ipados. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27821/ (Markdown: https://insights.sbomify.com/CVE-2024-27821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27821
- OSV: https://osv.dev/vulnerability/CVE-2024-27821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27821/
Summaries are generated and may contain mistakes; the official description above is the record.