# CVE-2026-32262: Craft CMS has a Path Traversal Vulnerability in AssetsController > Authenticated users with replaceFiles permission can delete arbitrary files on the local filesystem via path traversal in the AssetsController. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Mar 2026 - **Updated:** 17 Mar 2026 - **Also known as:** GHSA-472v-j2g4-g9h2 ## What is CVE-2026-32262? CVE-2026-32262 is a medium-severity path traversal vulnerability in Craftcms Craft Cms, published on 16 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Craft CMS is a content management system (CMS). From version 4.0.0-RC1 to before version 4.17.5 and from version 5.0.0-RC1 to before version 5.9.11, the AssetsController->replaceFile() method has a targetFilename body parameter that is used unsanitized in a deleteFile() call before Assets::prepareAssetName() is applied on save. This allows an authenticated user with replaceFiles permission to delete arbitrary files within the same filesystem root by injecting ../ path traversal sequences into the filename. This could allow an authenticated user with replaceFiles permission on one volume to delete files in other folders/volumes that share the same filesystem root. This only affects local filesystems. This issue has been patched in versions 4.17.5 and 5.9.11. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-32262? 4 open source packages ship an affected version, including craftcms/cms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.17.5 | | `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.17.5 | | `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.9.11 | | `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.9.11 | Products: Craftcms Craft Cms. ## How do I fix CVE-2026-32262? Upgrade craftcms/cms to a fixed version for your release line: 4.17.5 or 5.9.11. ## Is CVE-2026-32262 being exploited? There is no known exploitation of CVE-2026-32262 in the wild and no public exploit code. ## Other vulnerabilities in Craftcms Craft Cms - [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild) - [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild) - [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild) - [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild) - [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32262 and fix it if it is affected. What it is: CVE-2026-32262 is a medium-severity path traversal vulnerability in Craftcms Craft Cms, published on 16 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32262 in the wild and no public exploit code. Affected packages and fixed versions: - craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.17.5 - craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.17.5 - craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.11 - craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.11 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-32262/ (Markdown: https://insights.sbomify.com/CVE-2026-32262/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32262 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32262 - OSV: https://osv.dev/vulnerability/CVE-2026-32262 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32262/ Summaries are generated and may contain mistakes; the official description above is the record.