# CVE-2026-1776: Camaleon CMS AWS Uploader Authenticated Path Traversal Arbitrary File Read

> Authenticated users can read arbitrary files via path traversal in the AWS S3 uploader, exposing sensitive server data.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 9 Mar 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jw5g-f64p-6x78

## What is CVE-2026-1776?

CVE-2026-1776 is a medium-severity path traversal vulnerability in owen2345 Camaleon CMS, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Camaleon CMS versions 2.4.5.0 through 2.9.0, prior to commit f54a77e, contain a path traversal vulnerability in the AWS S3 uploader implementation that allows authenticated users to read arbitrary files from the web server’s filesystem. The issue occurs in the download_private_file functionality when the application is configured to use the CamaleonCmsAwsUploader backend. Unlike the local uploader implementation, the AWS uploader does not validate file paths with valid_folder_path?, allowing directory traversal sequences to be supplied via the file parameter. As a result, any authenticated user, including low-privileged registered users, can access sensitive files such as /etc/passwd. This issue represents a bypass of the incomplete fix for CVE-2024-46987 and affects deployments using the AWS S3 storage backend.

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

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

2 open source packages ship an affected version, including camaleon_cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `camaleon_cms` | RubyGems | From 2.4.5.0 to 2.9.1 | None |
| `camaleon_cms` | RubyGems | From 2.4.5.0 to 2.9.1 | None |

Products: Tuzitio Camaleon Cms.

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

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

## Is CVE-2026-1776 being exploited?

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

## Other vulnerabilities in owen2345 Camaleon CMS

- [CVE-2024-46986](https://insights.sbomify.com/CVE-2024-46986/): Arbitrary file write leading to RCE in Camaleon CMS (critical 10.0)
- [CVE-2023-30145](https://insights.sbomify.com/CVE-2023-30145/): Server-Side Template Injection in Camaleon CMS (critical 9.8)
- [CVE-2021-25970](https://insights.sbomify.com/CVE-2021-25970/): Camaleon CMS - Insufficient Session Expiration after Password Change (high 8.8)
- [CVE-2024-46987](https://insights.sbomify.com/CVE-2024-46987/): Arbitrary path traversal in Camaleon CMS (high 7.7)
- [CVE-2021-25969](https://insights.sbomify.com/CVE-2021-25969/): Camaleon CMS - Stored Cross-Site Scripting (XSS) in Comments (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1776 is a medium-severity path traversal vulnerability in owen2345 Camaleon CMS, published on 9 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-1776 in the wild and no public exploit code.

Affected packages and fixed versions:
- camaleon_cms (RubyGems): affected from 2.4.5.0 up to 2.9.1; no fix listed
- camaleon_cms (RubyGems): affected from 2.4.5.0 up to 2.9.1; no fix listed

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

## Sources

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

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