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.
Published: 2026-04-15
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Data Exposure
Action: Apply Patch
AI Analysis

Impact

Pyroscope can be configured to use Tencent Cloud Object Storage as a backend, and the configuration value for the secret_key that authorizes access to that storage is returned in plaintext through the API. If an attacker obtains the secret_key, the attacker can authenticate to the Tencent COS bucket, potentially reading, writing, or deleting data stored there, thereby compromising the confidentiality and integrity of the data in the cloud storage.

Affected Systems

Grafana:Pyroscope versions before 1.15.2, before 1.16.1, and before 1.17.0 are vulnerable. These versions include 1.15.x , 1.16.x , 1.17.x and earlier releases lacking the fix. Any deployment using those older versions with the Tencent COS backend must be considered affected.

Risk and Exploitability

The CVSS score is 9.1, indicating a critical severity. The EPSS score is not available, but the vulnerability is not listed in the CISA KEV catalog. An attacker needs direct access to the Pyroscope API, which typically requires the API to be reachable from an external or internal network. When such access exists, the attacker can exploit the exposed secret_key to compromise the underlying cloud object storage, leading to significant data exposure.

Generated by OpenCVE AI on April 15, 2026 at 21:55 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Pyroscope to 1.15.2 or later, 1.16.1 or later, or 1.17.0 or later.
  • Restrict access to the Pyroscope API so that only trusted users or internal systems can reach it, using firewall rules or network segmentation.
  • If Tencent COS backend is not required, disable or remove that configuration to eliminate the exposure risk.

Generated by OpenCVE AI on April 15, 2026 at 21:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-m9hq-h476-h2g8 Exposure of Storage Secret in Pyroscope
History

Thu, 16 Apr 2026 09:30:00 +0000

Type Values Removed Values Added
First Time appeared Grafana
Grafana pyroscope
Vendors & Products Grafana
Grafana pyroscope

Wed, 15 Apr 2026 22:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Wed, 15 Apr 2026 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 15 Apr 2026 19:30:00 +0000

Type Values Removed Values Added
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.
Title Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Grafana Pyroscope
cve-icon MITRE

Status: PUBLISHED

Assigner: GRAFANA

Published:

Updated: 2026-04-15T19:33:10.329Z

Reserved: 2025-04-16T09:19:26.443Z

Link: CVE-2025-41118

cve-icon Vulnrichment

Updated: 2026-04-15T19:32:59.983Z

cve-icon NVD

Status : Received

Published: 2026-04-15T20:16:32.933

Modified: 2026-04-15T20:16:32.933

Link: CVE-2025-41118

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-16T09:12:14Z

Weaknesses