CVE-2025-41118

Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection

Published Apr 15, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-m9hq-h476-h2g8 Pyroscope Exposes Storage Secret
History
Type Values Removed Values Added
CPEs cpe:2.3:a:grafana:pyroscope:*:*:*:*:*:*:*:*
cpe:2.3:a:grafana:pyroscope:1.16.0:*:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-732
Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
First Time appeared Grafana
Grafana pyroscope
Vendors & Products Grafana
Grafana pyroscope
Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
Metrics ssvc

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

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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GRAFANA
Published
Updated
Aug 27, 2026, 5:22 PM
Reserved
Apr 16, 2025, 9:19 AM
Status
Modified
Published
Apr 15, 2026, 8:16 PM
Modified
Oct 7, 2026, 9:10 AM
Severity
Important
Public date
Apr 15, 2026, 7:15 PM