Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

CVE-2026-85295: Chartbrew lets attacker hijack accounts with weak secret

CVE-2026-85295 · published 13 days ago
Summary

Chartbrew versions before 5.2.3 accept session tokens signed with a default or easy-to-guess secret key. If the secret is left unchanged, an attacker can create a fake token that lets them act as any user, bypassing passwords and two‑factor authentication. Update to version 5.2.3 and set a strong, unique secret key to resolve the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
chartbrew chartbrew < 5.2.3
Original advisory text
Chartbrew: Full account takeover via JWTs accepted under default CB_SECRET
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, four authentication helpers accepted session tokens signed with CB_SECRET, including known, weak, or shipped-default values. The vulnerable surface is session JWT fallback in server/modules/verifyToken.js, verifyUser.js, getUserFromToken.js, and socketManager.js across the API and socket layer. A stock source or repository Docker Compose deployment retains a known, weak, or default CB_SECRET and an attacker submits a forged HS256 token decoding to a target user id. Knowing the symmetric secret lets the attacker create a token that the legacy verification fallback accepts as the target user without that user's password or two-factor authentication. The condition includes stock source and repository Docker Compose installs and any otherwise known or weak CB_SECRET; a bare container where CB_SECRET is undefined is not affected by this fallback path. A forged session impersonates the chosen user across the entire API and socket layer and exercises that user's Chartbrew privileges. This issue is fixed in version 5.2.3.
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker full control
Severity
9.8 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-1394Use of Default Cryptographic Key
Timeline
Published6 Nov 2026
Updated18 Nov 2026
First seen6 Nov 2026
Sources
CVE-2026-85295 · MITRE
Track software like this
Free during beta