# CVE-2026-28889: A permissions issue was addressed with additional restrictions.


- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-92fw-jwv6-qxx7

## What is CVE-2026-28889?

CVE-2026-28889 is a medium-severity vulnerability in Apple Xcode, published on 25 Mar 2026. 

### Official description

A permissions issue was addressed with additional restrictions. This issue is fixed in Xcode 26.4. An app may be able to read arbitrary files as root.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-28889?

It affects 1 product.


Products: Apple Xcode.

## How do I fix CVE-2026-28889?

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

## Is CVE-2026-28889 being exploited?

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

## Other vulnerabilities in Apple Xcode

- [CVE-2025-48384](https://insights.sbomify.com/CVE-2025-48384/): Git Link Following (high 8.1, exploited in the wild)
- [CVE-2014-9390](https://insights.sbomify.com/CVE-2014-9390/): JGit Improper Input Validation vulnerability (critical 9.8)
- [CVE-2019-14379](https://insights.sbomify.com/CVE-2019-14379/): Deserialization of untrusted data in FasterXML jackson-databind (critical 9.8)
- [CVE-2018-4164](https://insights.sbomify.com/CVE-2018-4164/): An issue was discovered in certain Apple products. (critical 9.8)
- [CVE-2016-0746](https://insights.sbomify.com/CVE-2016-0746/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28889 and fix it if it is affected.

What it is: CVE-2026-28889 is a medium-severity vulnerability in Apple Xcode, published on 25 Mar 2026. 
Exploitation: There is no known exploitation of CVE-2026-28889 in the wild and no public exploit code.

Affected product: Apple Xcode. 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-2026-28889/ (Markdown: https://insights.sbomify.com/CVE-2026-28889/index.md)
```

## Sources

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

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