Grafana Pyroscope 1.16.0
Approved changes feed: RSS · Atom
cpe:2.3:a:grafana:pyroscope:1.16.0:*:*:*:*:*:*:*
part: a version: 1.16.0 update: *
| Vendor | Grafana (7564912d-bb81-50cf-9eb9-f573ac2fa519) |
|---|---|
| Product | Pyroscope (05bf2350-9070-5541-a101-609f6a144931) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/grafana/pyroscope-dotnet |
purl2cpe | 2026-06-01 10:14:45.203440 |
pkg:golang/github.com/grafana/pyroscope-dotnet |
purl2cpe | 2026-06-01 10:14:45.203442 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-41118 |
vulnerable | 2026-06-03 15:01:14.542461 |
Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection
CRITICAL (9.1)
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-15T19:15:17.689Z
Updated: 2026-05-13T19:28:46.050Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.