Critical RCE in Pyroscope's Tencent COS Backend
A critical vulnerability, tracked as CVE-2025-41118, has been identified in Pyroscope, an open-source continuous profiling database. According to the National Vulnerability Database, this flaw carries a CVSS score of 9.1, classifying it as critical.
The vulnerability surfaces when Pyroscope is configured to use Tencent Cloud Object Storage (COS) as its storage backend. An attacker with direct access to the Pyroscope API could exploit this weakness to extract the secret_key configuration value. While direct API access is a prerequisite, it underscores the importance of stringent network segmentation and access controls for database instances.
Patches are available across several Pyroscope release lines. Users on the 1.15.x branch should upgrade to version 1.15.2 or higher. For those on 1.16.x, version 1.16.1 and above address the issue. All versions in the 1.17.x series are already patched. The National Vulnerability Database credits Théo Cusnir for reporting this vulnerability via a bug bounty program.
Related ATT&CK Techniques
🛡️ Detection Rules
4 rules · 6 SIEM formats4 auto-generated detection rules for this incident, mapped to MITRE ATT&CK. Available in Sigma, Splunk SPL, Sentinel KQL, Elastic Lucene, QRadar AQL, and Wazuh.
Credential Abuse from Breached Vendor — CVE-2025-41118
Want this in your SIEM's native format? Get Splunk SPL, Sentinel KQL, Elastic, QRadar AQL, or Wazuh — ready to paste.
4 Sigma rules mapped to the ATT&CK techniques from this breach — pick your SIEM and get a ready-to-paste query.
Get All SIEM Formats →Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| CVE-2025-41118 | Information Disclosure | Pyroscope database configured with Tencent COS storage backend |
| CVE-2025-41118 | Information Disclosure | Pyroscope API secret_key extraction |
| CVE-2025-41118 | Misconfiguration | Pyroscope versions < 1.15.2, < 1.16.1, < 1.17.0 |