EUVD-2026-46067
GHSA-687c-pppw-76h3
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PR:L because a valid team member account is required; S:C and C:H because the SSRF's primary impact is on subsequent internal systems, not the HyperDX server itself; I:N and A:N because no integrity or availability impact is described.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Server-side request forgery in HyperDX before 2.31.0 allows authenticated team members to redirect the application server to arbitrary internal network destinations by supplying a caller-controlled host parameter to the ClickHouse proxy test endpoint, which performed no URL validation, protocol restriction, or private IP blocklist enforcement. The endpoint further reflected raw error response bodies back to the caller, enabling exfiltration of responses from internal APIs, container services, and cloud provider instance metadata endpoints such as AWS IMDSv1. No public exploit code has been identified and the vulnerability is not in CISA KEV, but the CVSS 4.0 vector assigns High confidentiality impact to subsequent systems (SC:H), reflecting serious internal infrastructure exposure potential for cloud-hosted deployments.
Technical ContextAI
HyperDX is an open-source observability platform (logs, metrics, traces) that uses ClickHouse as its analytics backend. The vulnerable component is the ClickHouse proxy test endpoint within the @hyperdx/api package, which accepted a caller-supplied host parameter to verify connectivity to a ClickHouse instance. Without protocol restriction, the endpoint could be directed to file://, gopher://, or other non-HTTP schemes. Without private IP validation, it could be directed to RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or link-local addresses (169.254.0.0/16), including cloud instance metadata services. The secondary exploitation vector was response reflection: error bodies from the proxied request were returned verbatim to the caller, converting a blind SSRF into a semi-blind or fully visible one. CWE-918 (Server-Side Request Forgery) precisely describes the root cause - the server acts as a proxy at the attacker's direction without constraining the target. The fix in commit 1705b37 adds the ip-address npm library for IP range checks, enforces http/https-only protocol validation via URL parsing, and suppresses raw error body reflection with a generic error message.
RemediationAI
Upgrade all HyperDX packages to version 2.31.0 or later. The patched release is available at https://github.com/hyperdxio/hyperdx/releases/tag/%40hyperdx%2Fapp%402.31.0 and the underlying fix commit is 1705b37ac68acc222cd038327ed79e167e256a1b. The fix adds private IP range blocking via the ip-address npm library, restricts the host parameter to http and https protocols only to eliminate file:// and gopher:// abuse, and removes raw error body reflection from the ClickHouse proxy endpoint and webhook test endpoints. If immediate patching is not possible, restrict access to the HyperDX API at the network perimeter so that only trusted personnel can reach the ClickHouse proxy test endpoint; this does not eliminate the vulnerability but reduces the attacker surface to personnel with legitimate network access. Additionally, enabling IMDSv2 (token-required mode) on AWS EC2 instances hosting HyperDX will prevent single-hop metadata exfiltration via SSRF, adding a meaningful compensating control with no functional side effects for the application.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today