CVE-2026-63731: HyperDX < 2.31.0 SSRF via ClickHouse Proxy Test Endpoint

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it 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.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-07-20).

Weakness: Server-Side Request Forgery (SSRF)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality none, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.003
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
Hyperdxio hyperdxfrom 2.0.0 before 2.31.0Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 2.31.0.

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-63731 HyperDX - Server-Side Request Forgery via ClickHouse proxy test host. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-63731 HyperDX - Server-Side Request Forgery via ClickHouse proxy test host"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/clickhouse-proxy/test"; nocase; fast_pattern; http.request_body; content:"host"; nocase; pcre:"/\x22host\x22\s*\x3a\s*\x22https?\x3a(?:\x2f\x2f|%2f%2f)?(?:127\.|0\.0\.0\.0|localhost|169\.254\.169\.254|metadata|10\.|192\.168\.|172\.(?:1[6-9]|2[0-9]|3[01])\.|\x5b)/i"; classtype:web-application-attack; reference:cve,CVE-2026-63731; reference:url,https://www.exploit.observer/?keyword=CVE-2026-63731&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=hyperdx&match=exact; sid:1095803; rev:1;)

CVE-2026-63731.rules on GitHub

References

Vendor advisories and patches

Exploit code

Technical analysis and advisories

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners