← Back to search

CVE-2026-85295

9.8 CRITICALpublic exploit available

Published 2026-11-06 · Updated 2026-11-09

AI risk analysis

Summary
Chartbrew versions prior to 5.2.3 are vulnerable to authentication bypass via forged JWT session tokens signed with weak or default CB_SECRET values, allowing attackers to impersonate any user—including admin—without credentials or MFA.
Exploitability
Exploitation is trivial for attackers who can obtain or guess a known/weak/default CB_SECRET (e.g., from stock Docker Compose deployments), requiring only JWT forgery and submission of the forged token.
Blast radius
Successful exploitation grants full API and socket-layer access as the impersonated user, enabling data exfiltration, configuration tampering, and full system compromise if the target has elevated privileges.
Detection
Monitor for repeated JWT verification failures with HS256 algorithm and mismatched issuer/subject claims in API and socket logs, especially when tokens decode to unexpected user IDs; also watch for anomalous bulk API requests from a single session that lacks prior authentication history.
Prioritized remediation
Upgrade to Chartbrew version 5.2.3 or later; for deployments where upgrading is not immediately possible, rotate CB_SECRET to a cryptographically strong random value and ensure it is never reused or exposed in configuration files or logs.
auth-bypassjwt-forgerydefault-credentialssession-hijackweb-app

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD 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, 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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CWE-1394

Public exploit & PoC references

All references

Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.

Related CVEs

Related by shared AI tags and CWE weakness class. Browse the full archive.