hyperdxio HyperDX up to 2.30.x ClickHouse proxy test endpoint host server-side request forgery

Summaryinfo

A vulnerability has been found in hyperdxio HyperDX up to 2.30.x and classified as problematic. Affected by this issue is some unknown functionality of the component ClickHouse proxy test endpoint. Performing a manipulation of the argument host results in server-side request forgery. This vulnerability was named CVE-2026-63731. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in hyperdxio HyperDX up to 2.30.x. It has been classified as problematic. This affects an unknown part of the component ClickHouse proxy test endpoint. The manipulation of the argument host with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality. The summary by CVE is:

HyperDX before 2.31.0 contains a server-side request forgery vulnerability that allows authenticated team members to direct the server to arbitrary internal destinations by supplying a caller-controlled host parameter to the ClickHouse proxy test endpoint with no URL validation or allowlist enforcement. Attackers can exploit the reflected error responses from the endpoint to disclose internal service response bodies, enabling access to internal APIs, container services, and cloud provider metadata endpoints.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-63731 since 07/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.31.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• hyperdxio

Name

• HyperDX

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30

Website

• Product: https://github.com/hyperdxio/hyperdx/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion