# CVE-2026-116009: Camaleon CMS before 2.9.3 Path Traversal RCE via Media crop_url Action


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wq77-q3hj-c75x

## What is CVE-2026-116009?

CVE-2026-116009 is a high-severity vulnerability in owen2345 camaleon-cms, published on 24 Oct 2026. 

### Official description

Camaleon CMS before 2.9.3 contains a path traversal vulnerability that allows users with only the media permission to write arbitrary files by supplying ../ sequences in the name parameter. Attackers can send a base64 data: URI to the crop_url media action to write an ERB template into a theme's views directory, which executes when rendered.

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

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


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

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

## Is CVE-2026-116009 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116009 is a high-severity vulnerability in owen2345 camaleon-cms, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116009 in the wild and no public exploit code.

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

## Sources

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

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