dbcve.org
PyroscopeApplication · Grafana

CVE-2025-41118

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to 1.15.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Pyroscope, an open-source continuous profiling database, exposes the Tencent COS storage backend's secret_key configuration value through its API when configured to use COS. An attacker with direct API access can retrieve this sensitive credential, enabling unauthorized access to the cloud storage bucket.

MitigationImmediately restrict network access to the Pyroscope API to trusted internal systems only. Upgrade to version 1.15.2+, 1.16.1+, or 1.17.0+ to apply the vendor fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PyroscopeApplication
Affected:< 1.15.2= 1.16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pyroscope version
    Check the running Pyroscope instance version through the /readyz or /debug/pprof endpoints, or check the binary/container version metadata
    Affected if version is below 1.15.2 or exactly 1.16.0
  2. Locate Pyroscope configuration
    Find the configuration file (typically pyroscope.yaml, config.yaml, or environment variables) used by the Pyroscope deployment
    Affected if configuration contains Tencent COS storage backend settings (such as 'cos' storage type, bucket names, or Tencent Cloud credentials)
  3. Verify COS secret_key is present in config
    Inspect the configuration for storage.backend settings pointing to Tencent COS, specifically looking for secret_key or related credential fields under the COS configuration section
    Affected if a secret_key value is defined in the COS storage configuration section
  4. Assess API accessibility
    Review network exposure of the Pyroscope HTTP API port (typically 4040). Check if the API is accessible from untrusted networks or the public internet through firewall rules, reverse proxy configurations, or cloud security groups
    Affected if the Pyroscope API is exposed to untrusted users or systems beyond the internal network

A user is affected if their Pyroscope version is below 1.15.2 or exactly 1.16.0, they have configured Tencent COS as the storage backend with a secret_key present, and the API is accessible to untrusted parties who could extract the credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.2 or later
Fixed in 1.15.2
Interim mitigation

Immediately restrict network access to the Pyroscope API to trusted internal systems only. Upgrade to version 1.15.2+, 1.16.1+, or 1.17.0+ to apply the vendor fix.

Recommended fix High confidence

1.15.2+, 1.16.1+, or 1.17.0+ (depending on current major version branch)

  1. Identify the current Pyroscope version running in your environment
  2. If currently on 1.15.x branch: upgrade to version 1.15.2 or later
  3. If currently on 1.16.x branch: upgrade to version 1.16.1 or later
  4. If currently on 1.17.x branch: upgrade to version 1.17.0 or later
  5. After upgrading, verify that the Tencent COS secret_key is no longer exposed via the Pyroscope API endpoint
  6. As a compensating control, ensure the Pyroscope API is not directly exposed to the public internet - limit access to trusted users and internal systems only
Caveat Minor security fix with no documented breaking changes; however, review release notes when upgrading across major branches (e.g., 1.16 to 1.17) for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pyroscope Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41118 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data