# CVE-2026-18751: Citrix Workspace App for Mac Security Bulletin for CVE-2026-18751

> An attacker can manipulate file names or paths in Citrix Workspace App for Mac, potentially reading or modifying unauthorized files.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-c292-w6wv-cjq9

## What is CVE-2026-18751?

CVE-2026-18751 is a medium-severity path traversal vulnerability in Citrix WorkSpace App, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

External control of file name or path vulnerability in Citrix WorkSpace App on MacOS.

This issue affects WorkSpace App: 2607.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-18751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18751 is a medium-severity path traversal vulnerability in Citrix WorkSpace App, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-18751 in the wild and no public exploit code.

Affected product: Citrix WorkSpace App. 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-18751/ (Markdown: https://insights.sbomify.com/CVE-2026-18751/index.md)
```

## Sources

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

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