# CVE-2026-64838: ICEcoder through 8.1 Path Traversal via oldFileName Parameter

> Authenticated attackers can exploit path traversal in ICEcoder to move files outside the document root, leading to file disclosure and deletion.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-3pmq-2635-wc4w

## What is CVE-2026-64838?

CVE-2026-64838 is a high-severity path traversal vulnerability in ICEcoder, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ICEcoder versions through 8.1 fail to properly validate the oldFileName parameter in file move and rename operations, allowing authenticated users to relocate files from outside the document root. Attackers can use path traversal sequences in oldFileName to move files writable by the PHP process into the web-accessible project directory, disclosing file contents and deleting originals.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-64838 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64838 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64838 is a high-severity path traversal vulnerability in ICEcoder, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64838 exists.

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

## Sources

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

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