GHSA-QP7J-X725-G67F

GHSA-QP7J-X725-G67F is a critical-severity security vulnerability in github.com/hydraide/hydraide (go), affecting versions >= 2.1.1, < 2.2.1. It is fixed in 2.2.1, 0.0.0-20250816184905-1256db38c33c.

Summary

There is no authentication of any kind.

Details

TLS is implemented, the tunnel between the client and server is secure, however once data is on the server, it's free to be read by any adversaries.

On the client side : https://github.com/hydraide/hydraide/blob/main/sdk/go/hydraidego/client/client.go#L221
It should be using a TLS Config with RootCAs and Certificates, currently RootCAs only (under NewClientTLSFromFile)

And on the server side, there should be ClientCAs and ClientAuth filled.

PoC

To bypass as is, the simplest way is to take the client and modify the code as such :

Modified from https://github.com/hydraide/hydraide/blob/main/sdk/go/hydraidego/client/client.go#L209

			// hostOnly := strings.Split(server.Host, ":")[0]
			// creds, certErr := credentials.NewClientTLSFromFile(server.CertFilePath, hostOnly)
			// if certErr != nil {
			// 	slog.Error("error while loading TLS credentials: ", "error", certErr, "server", server.Host, "fromIsland", server.FromIsland, "toIsland", server.ToIsland)
			// 	errorMessages = append(errorMessages, certErr)
			// }
			var opts []grpc.DialOption
			tlsConfig := &tls.Config{
				InsecureSkipVerify: true,
			}
			creds := credentials.NewTLS(tlsConfig)
			opts = append(opts, grpc.WithTransportCredentials(creds))

Resolution

This vulnerability has been fully fixed in server/v2.2.1 together with hydraidectl/v0.2.1.

All users are strongly advised to upgrade:

  1. Update to hydraidectl v0.2.1
  2. Re-initialize server instances with hydraidectl init into a new folder. This generates the required certificate files, downloads the latest binaries, and sets up the necessary environment variables.

For migration help, join the community Discord: https://discord.gg/xE2YSkzFRm or open a GitHub Discussion.
If anything does not work, please report it.

Impact

It impacts everyone who think there is any kind of authentication.

GHSA-QP7J-X725-G67F has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.1, 0.0.0-20250816184905-1256db38c33c); upgrading removes the vulnerable code path.

Affected versions

github.com/hydraide/hydraide (>= 2.1.1, < 2.2.1) github.com/hydraide/hydraide (< 0.0.0-20250816184905-1256db38c33c)

Security releases

github.com/hydraide/hydraide → 2.2.1 (go) github.com/hydraide/hydraide → 0.0.0-20250816184905-1256db38c33c (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/hydraide/hydraide to 2.2.1 or later; github.com/hydraide/hydraide to 0.0.0-20250816184905-1256db38c33c or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-QP7J-X725-G67F? GHSA-QP7J-X725-G67F is a critical-severity security vulnerability in github.com/hydraide/hydraide (go), affecting versions >= 2.1.1, < 2.2.1. It is fixed in 2.2.1, 0.0.0-20250816184905-1256db38c33c.
  2. How severe is GHSA-QP7J-X725-G67F? GHSA-QP7J-X725-G67F has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of github.com/hydraide/hydraide are affected by GHSA-QP7J-X725-G67F? github.com/hydraide/hydraide (go) versions >= 2.1.1, < 2.2.1 is affected.
  4. Is there a fix for GHSA-QP7J-X725-G67F? Yes. GHSA-QP7J-X725-G67F is fixed in 2.2.1, 0.0.0-20250816184905-1256db38c33c. Upgrade to this version or later.
  5. Is GHSA-QP7J-X725-G67F exploitable, and should I be worried? Whether GHSA-QP7J-X725-G67F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-QP7J-X725-G67F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-QP7J-X725-G67F?
    • Upgrade github.com/hydraide/hydraide to 2.2.1 or later
    • Upgrade github.com/hydraide/hydraide to 0.0.0-20250816184905-1256db38c33c or later

Other vulnerabilities in github.com/hydraide/hydraide

Stop the waste.
Protect your environment with Kodem.