Camaleon CMS vulnerable to Path Traversal through AWS S3 uploader implementation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-1776: 0.78% estimated exploitation activity in the next 30 days; percentile 55.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Camaleon CMS versions 2.4.5.0 through 2.9.1, 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 downloadprivatefile 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 validfolderpath?, 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.

Published by the source

10 Mar 2026, 09:31 UTC

Last modified by the source

24 Apr 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:51 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jw5g-f64p-6x78

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-1776

Advisory: Camaleon CMS vulnerable to Path Traversal through AWS S3 uploader implementation
IDs: CVE-2026-1776, GHSA-jw5g-f64p-6x78
Record: https://patchnext.com/advisories/cve-2026-1776 (revision 1, source checked 26 Oct 2026, 15:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems camaleon_cms: affected >= 2.4.5.0, <= 2.9.1

## Suggested inspection (read-only)
- RubyGems camaleon_cms: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on camaleon_cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jw5g-f64p-6x78 (GitHub-reviewed advisory GHSA-jw5g-f64p-6x78 lists affected ranges: RubyGems camaleon_cms >=2.4.5.0 <=2.9.1)

Commands are suggestions: review each one before running it.