Grafana · Grafana · published 2026-04-15
CVE-2025-41118Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection
Routine No exploitation evidence; EPSS 0.4%.
CVE-2025-41118 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 36% of all CVEs. This Grafana vulnerability: CVSS 9.1 (v3.1), attacks can be automated, a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
ObservabilityGrafana
Grafana: Exposure of Storage Secret in Pyroscope
Why: Vendor security release for server software (most severe: CVE-2025-41118).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (37th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.1 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Grafana Pyroscope
1.0.0to before1.16.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.