Skip to main content
VulnerabilityPublished

CVE-2026-85736: chartbrew · External Control of File Name or Path

Affects chartbrewSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 5.2.3 soon.

Data as of 6 Nov 2026, 21:19 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.1
Patch
Available – fixed in 5.2.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade chartbrew to 5.2.3.

Affected software

ProductAffectedFixed in
chartbrewchartbrewAffected
  • <5.2.3
Fixed in
  • 5.2.3

AI-suggested

Upgrade Chartbrew to version 5.2.3 or later, where this vulnerability is fixed. Deployments running Chartbrew as a less-privileged user will have limited impact based on that user's file deletion permissions. No other mitigations are specified or required once patched.

Description

CVE-2026-85736 is a high-severity vulnerability in Chartbrew prior to version 5.2.3. It involves external control of file paths used during cleanup of SSL and SSH certificate files when a data connection is deleted. An attacker with permissions to create and delete connections on their own team can supply arbitrary absolute file paths, which are then passed to the file unlink operation without restriction. This can lead to deletion of critical files such as application source code or environment configuration, resulting in integrity loss and service disruption. The issue is fixed in Chartbrew version 5.2.3.

References

Community reviews

Loading reviews…