Security Digest · Vulnerability record
CVE-2025-41118: Pyroscope Exposes Storage Secret
Pyroscope is an open-source continuous profiling database.
CVSS 9.1 Critical EPSS 0.4% · p34
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.4%, percentile 34: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 34% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
github.com/grafana/pyroscope(Go) < 1.15.2, fixed in 1.15.2;github.com/grafana/pyroscope(Go) >= 1.16.0, < 1.16.1, fixed in 1.16.1. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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).
Weakness type: CWE-732, CWE-201, CWE-200.
Product: github.com/grafana/pyroscope (Go) · Assigned by: GRAFANA · Published: 2026-04-15
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/grafana/pyroscope | < 1.15.2 | 1.15.2 |
| Go | github.com/grafana/pyroscope | >= 1.16.0, < 1.16.1 | 1.16.1 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Grafana | Pyroscope | 1.0.0 < 1.16.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GRAFANA | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| redhat-SADP | 3.1 | 7.5 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.41% probability of exploitation activity in the next 30 days; percentile 34.
Timeline
- — CVE record published by GRAFANA
- — GitHub-reviewed advisory GHSA-m9hq-h476-h2g8 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- grafana.com grafana.com
- access.redhat.com access.redhat.com
Vulnerability records
- GitHub Advisory GHSA-m9hq-h476-h2g8 github.com
- CVE.org record CVE-2025-41118 cve.org
- NVD entry CVE-2025-41118 nvd.nist.gov
Other references from the CVE record and advisory
- access.redhat.com access.redhat.com
- RHBZ#2458796 bugzilla.redhat.com
- security.access.redhat.com security.access.redhat.com