Quick answers
- Is CVE-2026-85726 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85726 being exploited in the wild.
- How severe is CVE-2026-85726?
- High severity, with a CVSS score of 7.5, published 6 November 2026.
- Which products and versions are affected?
- Chartbrew before 5.2.3.
- Is there a fix for CVE-2026-85726?
- Yes: fixed in 5.2.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85726 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85726?
- 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
Technical details
A date-typed MongoDB variable placed inside a quoted query placeholder is inserted as an unescaped string, unlike properly escaped string, number, and Boolean branches. An unauthenticated user can supply a crafted URL filter to a public, shareable, or embedded MongoDB chart, causing the date value to break out of the quoted literal and alter query semantics. The attack uses the chart's returned row count as a Boolean oracle for read-only field extraction from the queried collection, limited to one collection per request but capable of disclosing any field including those not displayed by the chart.
Affected products
- Chartbrew Chartbrew before 5.2.3
Timeline
- 2026-11-06: disclosed