Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-v6v8-xj6m-xwqh

MEDIUMFix: hashicorp/go-retryablehttp@a99f07b

GHSA-v6v8-xj6m-xwqh is a medium-severity (CVSS 6) CWE-532 vulnerability in github.com/hashicorp/go-retryablehttp. O3 Security confirms whether GHSA-v6v8-xj6m-xwqh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

go-retryablehttp can leak basic auth credentials to log files

Also known asCVE-2024-6104GO-2024-2947
Published
Jun 24, 2024
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/hashicorp/go-retryablehttp

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

go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/go-retryablehttpall versions0.7.7

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/go-retryablehttp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/hashicorp/go-retryablehttp to 0.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6v8-xj6m-xwqh is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-v6v8-xj6m-xwqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v6v8-xj6m-xwqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.
O3 Security · Impact-Aware SCA

Is GHSA-v6v8-xj6m-xwqh in your dependencies?

O3 detects GHSA-v6v8-xj6m-xwqh across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.