Chartbrew: Arbitrary file deletion as root via data connection SSL/SSH paths
Chartbrew server versions up to and including 5.2.2 are affected when self-signup is enabled, which is the default, and the container runs as root, which is the Docker image default. The fix is in 5.2.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Chartbrew server versions up to and including 5.2.2 are affected Default self-signup is enabled, so users are teamOwner of their own team with connection create and delete The container process runs as root (docker image default)
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Chartbrew, an open-source web app for building charts from databases and APIs, has an arbitrary file deletion flaw in how it cleans up data connection SSL and SSH key files. A logged-in user can be reached remotely, without user interaction, and can delete arbitrary files, such as application configuration or source code, which can cause integrity loss and service disruption.
Read the original description
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, connection creation or update stored attacker-chosen absolute SSL and SSH file paths, and later connection cleanup passed those stored paths to fs.unlink without a path restriction. The vulnerable surface is data-connection certificate and SSH-key cleanup when a connection is removed. A user with createOwn and deleteOwn permissions on their own team stores a target path in a connection and then deletes the connection to trigger cleanup; default self-signup grants teamOwner these permissions. The cleanup routine treats the stored SSL or SSH path as a managed certificate path and unlinks the referenced file; duplicateConnection provides a second advisory-identified trigger. The attacker must be able to create or update and then delete a connection on their own team. The default container runs Chartbrew as uid 0, while deployments with a less-privileged process are limited by that process's deletion permissions. The attacker can delete files such as /code/.env or application source, causing integrity loss and service disruption. This issue is fixed in version 5.2.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Chartbrew server versions up to and including 5.2.2 are affected Default self-signup is enabled, so users are teamOwner of their own team with connection create and delete The container process runs as root (docker image default)Upgrade to a fixed version: 5.2.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- chartbrew chartbrew
fixed in 5.2.3
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-85736
Is CVE-2026-85736 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user who can create and delete data connections can make the server delete arbitrary files by supplying paths for SSL or SSH settings. Because the process runs as root, any absolute path can be removed, which can break the application or destroy its configuration and source files.Source: github.com
Which versions are affected by CVE-2026-85736?
chartbrew: before 5.2.3.Source: cve.now feed data
Am I affected, and how do I check?
Chartbrew server versions up to and including 5.2.2 are affected. The relevant setup is default self-signup, where each new user becomes teamOwner of their own team with connection create and delete rights, and a container process running as root, which is the Docker image default. To check a version, look at the Chartbrew server release in use.Source: github.com
How do I fix CVE-2026-85736?
Upgrade the Chartbrew server to version 5.2.3 or later, which is the listed fixed version.Source: github.com