# CVE-2025-22247: Insecure file handling vulnerability > A local attacker with non-admin privileges can tamper with files to trigger insecure operations, potentially leading to privilege escalation or code execution. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 May 2025 - **Updated:** 18 Nov 2025 - **Also known as:** ALBA-2025:20841, ALSA-2025:A001, ALSA-2025:A002, ALSA-2025:A003, AZL-67797, AZL-67806, CLSA-2025-1751133361, DEBIAN-CVE-2025-22247, DLA-4165-1, DSA-5919-1, GHSA-mqmq-2p8r-q32f, MGASA-2025-0166, RHBA-2025:20841, RHBA-2026:0860, SUSE-SU-2025:01565-1, SUSE-SU-2025:01658-1, SUSE-SU-2025:01778-1, SUSE-SU-2025:1565-1, SUSE-SU-2025:20379-1, SUSE-SU-2025:20452-1, UBUNTU-CVE-2025-22247, USN-7508-1, USN-7508-2, openSUSE-SU-2025:15090-1 ## What is CVE-2025-22247? CVE-2025-22247 is a medium-severity path traversal vulnerability in VMware Tools, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description VMware Tools contains an insecure file handling vulnerability. A malicious actor with non-administrative privileges on a guest VM may tamper the local files to trigger insecure file operations within that VM. Weakness: CWE-59 (Improper Link Resolution Before File Access) ## Which versions are affected by CVE-2025-22247? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `open-vm-tools` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools-desktop` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools-devel` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools-salt-minion` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools-sdmp` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools-test` | AlmaLinux:10 | All versions | 12.5.0-1.el10.alma.1 | | `open-vm-tools` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools-desktop` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools-devel` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools-salt-minion` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools-sdmp` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools-test` | AlmaLinux:8 | All versions | 12.3.5-2.el8.alma.1 | | `open-vm-tools` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools` | AlmaLinux:9 | All versions | 13.0.0-1.el9_7.1 | | `open-vm-tools-desktop` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools-desktop` | AlmaLinux:9 | All versions | 13.0.0-1.el9_7.1 | | `open-vm-tools-devel` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools-salt-minion` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools-salt-minion` | AlmaLinux:9 | All versions | 13.0.0-1.el9_7.1 | | `open-vm-tools-sdmp` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools-sdmp` | AlmaLinux:9 | All versions | 13.0.0-1.el9_7.1 | | `open-vm-tools-test` | AlmaLinux:9 | All versions | 12.5.0-1.el9.alma.1 | | `open-vm-tools-test` | AlmaLinux:9 | All versions | 13.0.0-1.el9_7.1 | | `open-vm-tools` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-desktop` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-desktop-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-salt-minion` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-sdmp` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-sdmp-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools-test-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.3.5-2.el8_10.2 | | `open-vm-tools` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-desktop` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-desktop-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-salt-minion` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-sdmp` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | | `open-vm-tools-sdmp-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:13.0.0-1.el9_7.1 | ## How do I fix CVE-2025-22247? Apply the vendor's patch. ## Is CVE-2025-22247 being exploited? There is no known exploitation of CVE-2025-22247 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22247 and fix it if it is affected. What it is: CVE-2025-22247 is a medium-severity path traversal vulnerability in VMware Tools, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-22247 in the wild and no public exploit code. Affected product: VMware Tools. 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-2025-22247/ (Markdown: https://insights.sbomify.com/CVE-2025-22247/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22247 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22247 - OSV: https://osv.dev/vulnerability/CVE-2025-22247 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22247/ Summaries are generated and may contain mistakes; the official description above is the record.