Vulnary
← back to the feed
Critical· 9.1official fix available

CVE-2025-41118

Pyroscope, an open-source continuous profiling database, can expose the secret_key used for Tencent Cloud Object Storage when the database is configured to use that backend. An attacker who can reach the Pyroscope API can read this key, potentially accessing the cloud storage. The issue is fixed in newer releases of Pyroscope.

publishedApr 15, 2026
last modifiedAug 3, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
33th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 19, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Grafana Pyroscope, including versions 1.15.x, 1.16.x, and 1.17.x. The vulnerability affects deployments configured to use Tencent Cloud Object Storage as the storage backend. The affected version 1.16.0 is explicitly listed.

02

Real-world impact

An attacker who can reach the Pyroscope API can read the secret_key used to access Tencent COS, giving them the ability to read, modify, or delete data stored in the cloud bucket. This could lead to loss of data confidentiality and integrity.

03

Why this severity

The CVSS score of 9.1 reflects that the flaw is exploitable over the network without authentication or user interaction, and it allows full compromise of confidentiality and integrity of the data stored in the backend.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Pyroscope to a fixed version: 1.15.2 or newer, 1.16.1 or newer, or 1.17.0 or newer.
  2. 02Restart the Pyroscope service to apply the update.
interim mitigations
  • Limit public internet exposure of the Pyroscope API so that it is only accessible by trusted users or internal systems.

NVD-referenced vendor advisory

05

Timeline

  1. Apr 15, 2026 · Apr 15, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 20, 2026 · 16d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Aug 3, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
CVE-2025-41118: Pyroscope, an open-source continuous profiling database, can expose th · Vulnary