Summary
Private tokens could appear in logs if context containing gRPC metadata is logged in github.com/grpc/grpc-go
Workarounds
If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.
Impact
This issue represents a potential PII concern. If applications were printing or logging a context containing gRPC metadata, the affected versions will contain all the metadata, which may include private information.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0
Frequently Asked Questions
- What is GHSA-XR7Q-JX4M-X55M? GHSA-XR7Q-JX4M-X55M is a low-severity security vulnerability in google.golang.org/grpc (go), affecting versions >= 1.64.0, < 1.64.1. It is fixed in 1.64.1.
- Which versions of google.golang.org/grpc are affected by GHSA-XR7Q-JX4M-X55M? google.golang.org/grpc (go) versions >= 1.64.0, < 1.64.1 is affected.
- Is there a fix for GHSA-XR7Q-JX4M-X55M? Yes. GHSA-XR7Q-JX4M-X55M is fixed in 1.64.1. Upgrade to this version or later.
- Is GHSA-XR7Q-JX4M-X55M exploitable, and should I be worried? Whether GHSA-XR7Q-JX4M-X55M 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-XR7Q-JX4M-X55M 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-XR7Q-JX4M-X55M? Upgrade
google.golang.org/grpcto 1.64.1 or later.