GHSA-m9hq-h476-h2g8 — pyroscope
CRITICALGHSA-m9hq-h476-h2g8 is a critical-severity (CVSS 9.1) CWE-732 vulnerability in github.com/grafana/pyroscope. A fix is available for github.com/grafana/pyroscope — see the affected versions and patch details below.
Pyroscope Exposes Storage Secret
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m9hq-h476-h2g8.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-m9hq-h476-h2g8 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/grafana/pyroscope🐹github.com/grafana/pyroscopeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/pyroscope | all versions | 1.15.2go get github.com/grafana/pyroscope@v1.15.2 |
| 🐹Go | github.com/grafana/pyroscope | ≥ 1.16.0&&< 1.16.1 | 1.16.1go get github.com/grafana/pyroscope@v1.16.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/pyroscope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/pyroscope to 1.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9hq-h476-h2g8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m9hq-h476-h2g8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m9hq-h476-h2g8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This flaw allows an attacker with direct access to the Pyroscope API to extract the Tencent Cloud Object Storage (COS) `secret_key` in plaintext when COS is configured as the storage backend. Due to this reason, this vulnerability has been rated with an important severity.
| Product | Fixed in | Advisory |
|---|---|---|
| Multicluster Global Hub 1.7.3 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779925273 | RHSA-2026:24503 |
Frequently Asked Questions
Is GHSA-m9hq-h476-h2g8 in your dependencies?
O3 Security finds GHSA-m9hq-h476-h2g8 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.