GHSA-m9hq-h476-h2g8 · Severity: critical · Ecosystem: go — Pyroscope Exposes Storage Secret
Pyroscope is an open-source continuous profiling database. The database supports various storage backends, including Tencent Cloud Object Storage (COS). If the database is configured to use Tencent COS as the storage backend, an attacker could extract the secret_key configuration value from the Pyroscope API. To exploit this vulnerability, an attacker needs direct access to the Pyroscope API. We highly recommend limiting the public internet exposure of all our databases, such that they are only accessible by trusted users or internal systems. This vulnerability is fixed in versions: 1.15.x: 1.15.2 and above. 1.16.x: 1.16.1 and above. 1.17.x: 1.17.0 and above (i.e. all versions). Thanks to Théo Cusnir for reporting this vulnerability to us via our bug bounty program.
Conclusion & alert: CVE-2025-41118 is rated Moderate Risk (47.8/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.41%). Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-06-30 | 0.34% | 0.41% | +0.07% |
| 2 | 2026-06-15 | 0.03% | 0.34% | +0.31% |
| 3 | 2026-04-16 | — | 0.03% | — |
Full EPSS history (3 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 9.1 | 3.1 | CRITICAL |
|
3.9 | 5.2 | [email protected] |
| 7.5 | 3.1 | HIGH |
|
3.9 | 3.6 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c |
GHSA-m9hq-h476-h2g8 · Severity: critical · Ecosystem: go — Pyroscope Exposes Storage Secret
| vendor | priority | summary | link |
|---|---|---|---|
redhat
|
high | — | https://access.redhat.com/security/cve/CVE-2025-41118 |