CVE-2025-41118: Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection
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 secretkey 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/grafana/pyroscopeto a version that resolves this vulnerability.Fixed in 1.16.1 - Upgrade
Upgrade
go/github.com/grafana/pyroscopeto a version that resolves this vulnerability.Fixed in 1.15.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.15.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.16.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.17.0 - Compensating control
Limit public internet exposure of the Pyroscope database so the Pyroscope API is only accessible by trusted users or internal systems.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-41118?
CVE-2025-41118 is considered a high-severity vulnerability due to the exposure of sensitive information.
How do I fix CVE-2025-41118?
To mitigate CVE-2025-41118, ensure type protection is implemented in the configuration API to secure the SecretKey.
Which software versions are affected by CVE-2025-41118?
CVE-2025-41118 affects Pyroscope versions 1.15.0 to 1.15.2 and 1.16.0 to 1.16.1.
What kind of data is exposed in CVE-2025-41118?
CVE-2025-41118 exposes the `SecretKey` in plaintext, which can lead to unauthorized access.
Who is the vendor associated with CVE-2025-41118?
The vendor associated with CVE-2025-41118 is Pyroscope.