CVE-2026-85295
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 35% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1394 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-120442 | Critical | 9.8 | 1.7% | - | - |
| CVE-2024-48956 | Critical | 9.8 | 0.9% | - | - |
| CVE-2020-37281 | High | 8.1 | 0.9% | - | - |
| CVE-2025-44954 | Critical | 9.0 | 0.7% | - | Fix |
| CVE-2024-11619 | Medium | 5.0 | 0.7% | - | - |
| CVE-2024-29037 | Critical | 9.1 | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-85295?
No published fix for CVE-2026-85295 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-85295 being actively exploited?
Not that we know of. CVE-2026-85295 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.40% is the estimated probability that it will be exploited in the next 30 days. That is higher than 35% of all scored CVEs.
How severe is CVE-2026-85295?
CVE-2026-85295 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-85295
Markdown
[](https://tridentstack.com/cve/CVE-2026-85295)HTML
<a href="https://tridentstack.com/cve/CVE-2026-85295"><img src="https://tridentstack.com/cve/badge/CVE-2026-85295.svg" alt="CVE-2026-85295"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-09.