LiveActive security incident?Get immediate response
CVE Record

CVE-2025-41118: Sensitive COS `SecretKey` exposed in plaintext via configuration API due to missing type protection

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Pyroscope deployments using Tencent Cloud Object Storage could expose the COS secret_key through the Pyroscope API. If that API is reachable by an untrusted party, the attacker may obtain cloud storage credentials. The vendor rates this critical and has released fixed versions.

Executive priority

Treat this as urgent where Pyroscope uses Tencent COS or its API is externally reachable. The business risk is cloud storage credential exposure, not service outage. Prioritize upgrade, access restriction, and key rotation decisions.

Technical view

The issue is a plaintext exposure of the Tencent COS secret_key configuration value through the Pyroscope API when COS is configured as storage. CVSS 3.1 is 9.1 with network access, low complexity, no privileges, and high confidentiality and integrity impact. Sources map it to CWE-201 and CWE-732.

Likely exposure

Exposure is most likely for Grafana Pyroscope instances configured with Tencent COS and reachable from the internet, partner networks, or other untrusted users. Instances not using Tencent COS are not described as exposed by the provided sources.

Exploitation context

The source bundle does not show KEV listing or active exploitation. Exploitation requires direct access to the Pyroscope API. The main risk is credential disclosure leading to misuse of Tencent COS storage access.

Researcher notes

Affected-version detail in the bundle is limited, but fixed versions are explicit: 1.15.2+, 1.16.1+, and all 1.17.x. Do not assume other storage backends are affected without vendor confirmation. No active exploitation evidence is provided.

Mitigation direction

  • Upgrade Pyroscope 1.15.x to 1.15.2 or later.
  • Upgrade Pyroscope 1.16.x to 1.16.1 or later.
  • Use Pyroscope 1.17.0 or later where applicable.
  • Restrict Pyroscope API access to trusted users or internal systems.
  • Rotate Tencent COS secret keys if API exposure is suspected.
  • Check Grafana and Red Hat advisories for environment-specific guidance.

Validation and detection

  • Inventory Pyroscope deployments and record versions.
  • Confirm whether Tencent COS is configured as the storage backend.
  • Verify the Pyroscope API is not publicly reachable.
  • Review access logs for untrusted API access before remediation.
  • Confirm upgraded instances meet the fixed version thresholds.
  • Assess whether exposed COS keys require rotation.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-732: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-41118 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2GRAFANA
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2025-41118Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPpyroscope: sensitive COS SecretKey exposed in plaintext via configuration API due to missing type protection
other:Red Hat severity ratingcvssV3_1
  • 2026-04-15T20:02:03.347Z: Reported to Red Hat.
  • 2026-04-15T19:15:17.689Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GrafanaPyroscope1.0.0unaffected
Weakness

CWE details

CWE-201CWE-732

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.