What is GHSA-HRXH-6V49-42GF?

GHSA-HRXH-6V49-42GF is a high-severity allocation of resources without limits or throttling vulnerability in google.golang.org/grpc (go), affecting versions < 1.82.1. It is fixed in 1.82.1. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which versions of google.golang.org/grpc are affected by GHSA-HRXH-6V49-42GF?

google.golang.org/grpc (go) versions < 1.82.1 is affected.

Is there a fix for GHSA-HRXH-6V49-42GF?

Yes. GHSA-HRXH-6V49-42GF is fixed in 1.82.1. Upgrade to this version or later.

Is GHSA-HRXH-6V49-42GF exploitable, and should I be worried?

Whether GHSA-HRXH-6V49-42GF 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.

What actually determines whether GHSA-HRXH-6V49-42GF 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.

How do I fix GHSA-HRXH-6V49-42GF?

Upgrade google.golang.org/grpc to 1.82.1 or later.

GHSA-HRXH-6V49-42GF in google.golang.org/grpc

Q: Which versions of google.golang.org/grpc are affected by GHSA-HRXH-6V49-42GF?

google.golang.org/grpc (go) versions < 1.82.1 is affected.

Q: Is there a fix for GHSA-HRXH-6V49-42GF?

Yes. GHSA-HRXH-6V49-42GF is fixed in 1.82.1. Upgrade to this version or later.

Q: Is GHSA-HRXH-6V49-42GF exploitable, and should I be worried?

Whether GHSA-HRXH-6V49-42GF 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.

Q: What actually determines whether GHSA-HRXH-6V49-42GF 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.

Q: How do I fix GHSA-HRXH-6V49-42GF?

Upgrade google.golang.org/grpc to 1.82.1 or later.

Summary

gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities

Impact

What kind of vulnerability is it? Who is impacted?

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

google.golang.org/grpc (< 1.82.1)

Security releases

google.golang.org/grpc → 1.82.1 (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.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Has the problem been patched? What versions should users upgrade to?

All three issues have been fixed in master and will be released in 1.82.1 shortly.

Frequently Asked Questions

What is GHSA-HRXH-6V49-42GF? GHSA-HRXH-6V49-42GF is a high-severity allocation of resources without limits or throttling vulnerability in google.golang.org/grpc (go), affecting versions < 1.82.1. It is fixed in 1.82.1. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which versions of google.golang.org/grpc are affected by GHSA-HRXH-6V49-42GF? google.golang.org/grpc (go) versions < 1.82.1 is affected.
Is there a fix for GHSA-HRXH-6V49-42GF? Yes. GHSA-HRXH-6V49-42GF is fixed in 1.82.1. Upgrade to this version or later.
Is GHSA-HRXH-6V49-42GF exploitable, and should I be worried? Whether GHSA-HRXH-6V49-42GF 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
What actually determines whether GHSA-HRXH-6V49-42GF 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.
How do I fix GHSA-HRXH-6V49-42GF? Upgrade google.golang.org/grpc to 1.82.1 or later.

Other vulnerabilities in google.golang.org/grpc

CVE-IDSeverityPackage summary

CVE-2026-33186Criticalgoogle.golang.org/grpc: gRPC-Go has an authorization bypass via missing leading slash in :path GHSA-XR7Q-JX4M-X55MLowgoogle.golang.org/grpc: Private tokens could appear in logs if context containing gRPC metadata is logged in github.com/grpc/grpc-go GHSA-M425-MQ94-257GHighgoogle.golang.org/grpc: gRPC-Go HTTP/2 Rapid Reset vulnerability