Read the docs
TI-2026-86128 Aliases CVE-2026-54589

Server-side request forgery bypass in Chartbrew API data connections

Priority LOW 31CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-918 and the CVSS impact.

Summary

Chartbrew before 5.2.1 does not recognize IPv4 addresses embedded in NAT64 prefixes in its outbound URL guard, which enables server-side request forgery (CWE-918). An authenticated user who can create or edit API connections can use a hostname that resolves to a NAT64 address embedding a private or link-local IPv4 address to read responses from internal hosts.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.1, the outbound URL guard recognized ordinary IPv4, IPv6, and IPv4-mapped IPv6 destinations but did not recognize IPv4 addresses embedded in NAT64 prefixes. The vulnerable surface is aPI Data Connection outbound requests routed through server/modules/outboundTargetPolicy.js. An authenticated user with permission to create or edit an API connection supplies an attacker-controlled hostname or redirect whose DNS answer is a NAT64 address embedding a private or link-local IPv4 destination. The policy treated the NAT64 address as public; a NAT64 gateway then translated it to the embedded private IPv4 address after validation. The bypass requires a NAT64/DNS64 deployment path and connection-management privileges. IPv4-only deployments are not affected by this specific bypass. The attacker can read responses from 169.254.169.254 cloud metadata and arbitrary internal IPv4 hosts and ports reachable through the NAT64 gateway. This issue is fixed in version 5.2.1.

Why it matters now

EPSS 0.00344 28th percentileScored 2026-11-07
Fix Fixed chartbrew (chartbrew): 5.2.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
chartbrewchartbrewbefore 5.2.15.2.1Patch availableCNA
  • chartbrew Vendorchartbrew Affected before 5.2.1 Fixed in 5.2.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:depomo:chartbrew:*:*:*:*:*:*:*:*——chartbrew
  • cpe:2.3:a:depomo:chartbrew:*:*:*:*:*:*:*:* Versions — — ·chartbrew

Remediation

Upgrade Chartbrew to version 5.2.1, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA chartbrew (chartbrew) Fixed in 5.2.1

Timeline

  1. 2026-11-06 Threatist record created from CVE-2026-54589
  2. 2026-11-08 Priority changed: MEDIUM → LOW

References

  • TI-2026-46993 Chartbrew: SQL Injection via Missing Backslash Escaping in ClickHouse Variable Substitution CVSS 4.0HIGH 7.9
  • TI-2026-29337 Chartbrew: Missing Authorization in /api/chart/:chart_id/query via team-level refresh toggle CVSS 3.1HIGH 7.5
  • TI-2026-29331 Chartbrew: Incorrect Access Control in public chart and export routes via missing onReport and SharePolicy checks CVSS 3.1HIGH 7.5
  • TI-2026-29560 Chartbrew: Incorrect Access Control in dataset and dataRequest routes via team-scoped permission checks CVSS 3.1HIGH 8.1
  • TI-2026-29336 Chartbrew: Incorrect Access Control in project share policy routes via unbound policy_id CVSS 3.1HIGH 8.1
  • TI-2026-24781 Chartbrew Cross-Tenant Template Export and Secret Disclosure in `GET /team/:team_id/template/generate/:project_id` CVSS 3.1HIGH 7.7
See all 29 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences