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

> Authenticated users can exploit an SSRF vulnerability in the ClickHouse proxy test endpoint to access internal services and cloud metadata.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-687c-pppw-76h3

## What is CVE-2026-63731?

CVE-2026-63731 is a medium-severity server-side request forgery vulnerability in hyperdxio hyperdx, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-63731?


## How do I fix CVE-2026-63731?

No fix has been published for CVE-2026-63731 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63731 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63731 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63731 and fix it if it is affected.

What it is: CVE-2026-63731 is a medium-severity server-side request forgery vulnerability in hyperdxio hyperdx, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63731 exists.

Affected product: hyperdxio hyperdx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63731/ (Markdown: https://insights.sbomify.com/CVE-2026-63731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63731
- OSV: https://osv.dev/vulnerability/CVE-2026-63731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63731/
Summaries are generated and may contain mistakes; the official description above is the record.