# CVE-2024-22260: Information disclosure in VMware Workspace One UEM

> A malicious actor with network access can exploit VMware Workspace One UEM to expose sensitive information.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-qr35-h6w8-mx66

## What is CVE-2024-22260?

CVE-2024-22260 is a medium-severity vulnerability in VMware Workspace One UEM, published on 27 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

VMware Workspace One UEM update addresses an information exposure vulnerability. 
A malicious actor with network access to the Workspace One UEM may be 
able to perform an attack resulting in an information exposure.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-22260 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22260 is a medium-severity vulnerability in VMware Workspace One UEM, published on 27 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22260 in the wild and no public exploit code.

Affected product: VMware Workspace One UEM. 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-22260/ (Markdown: https://insights.sbomify.com/CVE-2024-22260/index.md)
```

## Sources

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

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