Is CVE-2026-85295 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85295 being exploited in the wild.

How severe is CVE-2026-85295?

Critical severity, with a CVSS score of 9.8, published 6 November 2026.

How is CVE-2026-85295 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-85295?

Check whether you run Chartbrew at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85295: Chartbrew authentication bypass via legacy session tokens

CVE-2026-85295 · Severity: critical · CVSS 9.8 · Published 2026-11-06

Chartbrew is an open-source web application that connects to databases and APIs to create charts. Prior to version 5.2.3, the application accepted session tokens signed with a weak or default cryptographic secret, allowing attackers to forge valid authentication tokens. An attacker with knowledge of the default secret can impersonate any user and gain full access to that user's data and privileges without knowing their password or bypassing two-factor authentication.

Technologies: Chartbrew. Vendors: Chartbrew.

Quick answers

Is CVE-2026-85295 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85295 being exploited in the wild.
How severe is CVE-2026-85295?: Critical severity, with a CVSS score of 9.8, published 6 November 2026.
Which products and versions are affected?: Chartbrew before 5.2.3.
Is there a fix for CVE-2026-85295?: Yes: fixed in 5.2.3. Until then: Ensure CB_SECRET is set to a strong, randomly generated value not the shipped default. Set CB_ALLOW_LEGACY_SHARE_TOKENS to false unless temporarily needed for migration of existing share links. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85295 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-85295?: Check whether you run Chartbrew at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 5.2.3

Ensure CB_SECRET is set to a strong, randomly generated value not the shipped default. Set CB_ALLOW_LEGACY_SHARE_TOKENS to false unless temporarily needed for migration of existing share links.

Technical details

The vulnerability exists in JWT session token verification across four server-side modules (verifyToken.js, verifyUser.js, getUserFromToken.js, socketManager.js) that fall back to accepting HS256 tokens signed with CB_SECRET, including known weak or shipped-default values. An attacker can forge a valid session JWT by signing it with the symmetric secret and specifying a target user ID, gaining impersonation across the entire API and socket layer. The issue affects stock source and Docker Compose deployments that retain the default CB_SECRET; only containers with CB_SECRET explicitly undefined are not vulnerable.

Affected products

Chartbrew Chartbrew before 5.2.3

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.