CVE-2025-41118
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.41%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 0.41% probability · 34th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-732, CWE-201
- Affected
- grafana/pyroscope
- Source
- security@grafana.com
References
- https://grafana.com/security/security-advisories/cve-2025-41118Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:24503
- https://access.redhat.com/security/cve/CVE-2025-41118
- https://bugzilla.redhat.com/show_bug.cgi?id=2458796
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-41118.json
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.