How severe is GHSA-xr7q-jx4m-x55m?

No CVSS score has been assigned to GHSA-xr7q-jx4m-x55m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xr7q-jx4m-x55m?

GHSA-xr7q-jx4m-x55m affects the following packages: google.golang.org/grpc (Go). Ecosystems affected: Go.

How do I fix GHSA-xr7q-jx4m-x55m?

Update google.golang.org/grpc to 1.64.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr7q-jx4m-x55m is resolved across your whole dependency graph.

How do I detect GHSA-xr7q-jx4m-x55m in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google.golang.org/grpc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xr7q-jx4m-x55m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-xr7q-jx4m-x55m actively exploited in the wild?

No public exploit code has been indexed for GHSA-xr7q-jx4m-x55m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xr7q-jx4m-x55m published, and has it been updated?

GHSA-xr7q-jx4m-x55m was published on July 5, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Private tokens could appear in logs if context containing gRPC metadata is logged in github.com/grpc/grpc-goGHSA-xr7q-jx4m-x55m

Fix: grpc/grpc-go@ab29241

GHSA-xr7q-jx4m-x55m is a security vulnerability in google.golang.org/grpc. A fix is available for google.golang.org/grpc — see the affected versions and patch details below.

Also known asGO-2024-2978

Published

Jul 5, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹google.golang.org/grpc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0

Workarounds

If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`google.golang.org/grpc`	≥ 1.64.0&&< 1.64.1	1.64.1`go get google.golang.org/grpc@v1.64.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google.golang.org/grpc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update google.golang.org/grpc to 1.64.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr7q-jx4m-x55m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. ### Patches The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0 ### Workarounds If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.

O3 Security · Impact-Aware SCA

Is GHSA-xr7q-jx4m-x55m in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works