CVE-2025-41118: Vulnerability in Grafana Pyroscope
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.
AI Analysis
Technical Summary
Pyroscope versions configured to use Tencent COS as a storage backend expose the secret_key configuration via the Pyroscope API if accessed by an attacker. This exposure requires the attacker to have direct API access. The vulnerability allows extraction of sensitive secret_key credentials, potentially compromising the confidentiality and integrity of the system. Fixed versions are 1.15.2 and above for 1.15.x, 1.16.1 and above for 1.16.x, and all 1.17.x versions starting from 1.17.0. The CVSS 3.1 score is 9.1 (critical), with attack vector network, low attack complexity, no privileges required, no user interaction, and high confidentiality and integrity impact.
Potential Impact
An attacker with direct access to the Pyroscope API can extract the secret_key configuration value when Tencent COS is used as the storage backend. This leads to a high confidentiality and integrity impact, as the secret_key could be used to compromise the storage backend or related systems. There is no reported impact on availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade Pyroscope to version 1.15.2 or later for the 1.15.x series, 1.16.1 or later for the 1.16.x series, or 1.17.0 or later for the 1.17.x series to remediate this vulnerability. Additionally, limit public internet exposure of the Pyroscope API to trusted users or internal systems to reduce the risk of exploitation. Patch status is confirmed by the vendor's advisory indicating fixed versions.
CVE-2025-41118: Vulnerability in Grafana Pyroscope
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Pyroscope versions configured to use Tencent COS as a storage backend expose the secret_key configuration via the Pyroscope API if accessed by an attacker. This exposure requires the attacker to have direct API access. The vulnerability allows extraction of sensitive secret_key credentials, potentially compromising the confidentiality and integrity of the system. Fixed versions are 1.15.2 and above for 1.15.x, 1.16.1 and above for 1.16.x, and all 1.17.x versions starting from 1.17.0. The CVSS 3.1 score is 9.1 (critical), with attack vector network, low attack complexity, no privileges required, no user interaction, and high confidentiality and integrity impact.
Potential Impact
An attacker with direct access to the Pyroscope API can extract the secret_key configuration value when Tencent COS is used as the storage backend. This leads to a high confidentiality and integrity impact, as the secret_key could be used to compromise the storage backend or related systems. There is no reported impact on availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade Pyroscope to version 1.15.2 or later for the 1.15.x series, 1.16.1 or later for the 1.16.x series, or 1.17.0 or later for the 1.17.x series to remediate this vulnerability. Additionally, limit public internet exposure of the Pyroscope API to trusted users or internal systems to reduce the risk of exploitation. Patch status is confirmed by the vendor's advisory indicating fixed versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GRAFANA
- Date Reserved
- 2025-04-16T09:19:26.443Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69dfe7b682d89c981f913c3c
Added to database: 4/15/2026, 7:32:06 PM
Last enriched: 4/15/2026, 7:46:56 PM
Last updated: 4/16/2026, 6:22:24 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.