Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2024-6104 — go-retryablehttp

MEDIUMFix: hashicorp/go-retryablehttp@a99f07b

CVE-2024-6104 is a medium-severity (CVSS 6) CWE-532 vulnerability in github.com/hashicorp/go-retryablehttp. A fix is available for github.com/hashicorp/go-retryablehttp — see the affected versions and patch details below.

go-retryablehttp can leak basic auth credentials to log files

Also known asGHSA-v6v8-xj6m-xwqhGO-2024-2947
Published
Jun 24, 2024
Updated
Aug 27, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-6104.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-6104 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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.7go get github.com/hashicorp/go-retryablehttp@v0.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 CVE-2024-6104 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-6104 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-6104. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
CLUSTER-OBSERVABILITY-OPERATOR-0.4-RHEL-8cluster-observability-operator/cluster-observability-operator-bundle:0.4.1-18RHSA-2024:8040
multicluster engine for Kubernetes 2.5 for RHEL 8multicluster-engine/hive-rhel8:v2.5.7-1RHSA-2024:6738
OpenShift Custom Metrics Autoscaler 2custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel8:2.14.1-454RHBA-2024:5865
OpenShift-Pipelines-1.16-RHEL-8openshift-pipelines-client-0:1.16.0-11647.el8RHEA-2024:7866
Red Hat Advanced Cluster Security 4.4advanced-cluster-security/rhacs-central-db-rhel8:4.4.5-2RHSA-2024:6054
Red Hat Ceph Storage 8.1rhceph/grafana-rhel9:11.5.2-6RHSA-2025:9776
Red Hat Enterprise Linux 8container-tools:rhel8-8100020240808093819.afee755dRHSA-2024:5258
Red Hat Enterprise Linux 8.8 Extended Update Supportcontainer-tools:rhel8-8080020240724065004.0f77c1b7RHSA-2024:5194

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 CVE-2024-6104 in your dependencies?

O3 Security finds CVE-2024-6104 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-6104: go-retryablehttp (Medium 6) | O3 Security