CVE-2025-41118

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:grafana, epss
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

April 15, 2026

Last Modified

August 27, 2026

Advisory Details (5)

Auto-updated Sep 7, 2026
Patch available.
generic Patch Available

Exposure of Storage Secret in Pyroscope | Grafana Labs

https://grafana.com/security/security-advisories/cve-2025-41118
redhat Patch Available

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-41118.json
redhat

2458796 – (CVE-2025-41118) CVE-2025-41118 pyroscope: sensitive COS SecretKey exposed in plaintext via configuration API due to missing type protection

https://bugzilla.redhat.com/show_bug.cgi?id=2458796
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2025-41118
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24503

Vendor Advisories for CVE-2025-41118(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/grafana/pyroscope—1.16.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 272 total refreshes for this CVE.

  1. 2026-09-13 16:46 UTCEPSS rescore
  2. 2026-09-12 15:00 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-11 09:35 UTCEPSS rescore
  5. 2026-09-10 09:33 UTCEPSS rescore
  6. 2026-09-08 21:59 UTCEPSS rescore
  7. 2026-09-07 16:00 UTCEPSS rescore
  8. 2026-09-06 13:46 UTCEPSS rescore
  9. 2026-09-04 05:05 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 13:53 UTCEPSS rescore
  12. 2026-09-01 04:38 UTCEPSS rescore
  13. 2026-08-30 19:16 UTCEPSS rescore
  14. 2026-08-30 01:21 UTCEPSS rescore
  15. 2026-08-28 21:40 UTCEPSS rescore
  16. 2026-08-27 18:04 UTCEG score recompute
  17. 2026-08-27 18:04 UTCVendor advisory
  18. 2026-08-27 14:24 UTCEPSS rescore
  19. 2026-08-26 14:45 UTCEPSS rescore
  20. 2026-08-26 09:17 UTCEG score recompute
  21. 2026-08-26 09:17 UTCVendor advisory
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:04 UTCEG score recompute
  24. 2026-08-24 14:04 UTCVendor advisory
  25. 2026-08-24 13:31 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:31 UTCVendor advisory
  2. 2026-08-24 12:26 UTCEG score recompute
  3. 2026-08-24 12:26 UTCVendor advisory
  4. 2026-08-23 00:18 UTCEPSS rescore
  5. 2026-08-21 23:48 UTCEPSS rescore
  6. 2026-08-20 22:54 UTCEPSS rescore
  7. 2026-08-19 19:15 UTCVendor advisory
  8. 2026-08-19 18:59 UTCVendor advisory
  9. 2026-08-19 17:52 UTCEG score recompute
  10. 2026-08-19 17:52 UTCVendor advisory
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-18 13:47 UTCEPSS rescore
  14. 2026-08-17 21:44 UTCEG score recompute
  15. 2026-08-17 21:44 UTCVendor advisory
  16. 2026-08-17 13:46 UTCEPSS rescore
  17. 2026-08-17 12:13 UTCEG score recompute
  18. 2026-08-17 12:13 UTCVendor advisory
  19. 2026-08-16 14:55 UTCEPSS rescore
  20. 2026-08-16 10:42 UTCVendor advisory
  21. 2026-08-16 06:39 UTCEG score recompute
  22. 2026-08-16 06:39 UTCVendor advisory
  23. 2026-08-16 02:13 UTCEPSS rescore
  24. 2026-08-15 02:30 UTCEG score recompute
  25. 2026-08-15 02:30 UTCVendor advisory
  26. 2026-08-15 01:29 UTCEPSS rescore
  27. 2026-08-14 22:20 UTCVendor advisory
  28. 2026-08-14 18:12 UTCVendor advisory
  29. 2026-08-14 12:50 UTCVendor advisory
  30. 2026-08-14 08:47 UTCVendor advisory
  31. 2026-08-14 04:44 UTCEG score recompute
  32. 2026-08-14 04:44 UTCVendor advisory
  33. 2026-08-13 21:59 UTCEPSS rescore
  34. 2026-08-13 08:56 UTCVendor advisory
  35. 2026-08-13 03:00 UTCVendor advisory
  36. 2026-08-12 22:57 UTCVendor advisory
  37. 2026-08-12 18:54 UTCEG score recompute
  38. 2026-08-12 18:54 UTCVendor advisory
  39. 2026-08-12 13:50 UTCEPSS rescore
  40. 2026-08-12 13:27 UTCVendor advisory
  41. 2026-08-11 22:58 UTCVendor advisory
  42. 2026-08-11 18:51 UTCEG score recompute
  43. 2026-08-11 18:51 UTCVendor advisory
  44. 2026-08-11 05:34 UTCEG score recompute
  45. 2026-08-11 05:34 UTCVendor advisory
  46. 2026-08-11 02:38 UTCEG score recompute
  47. 2026-08-11 02:38 UTCVendor advisory
  48. 2026-08-10 13:21 UTCEG score recompute
  49. 2026-08-10 13:21 UTCVendor advisory
  50. 2026-08-10 12:26 UTCEG score recompute
  51. 2026-08-10 12:26 UTCVendor advisory
  52. 2026-08-10 09:03 UTCVendor advisory
  53. 2026-08-10 04:58 UTCVendor advisory
  54. 2026-08-10 00:55 UTCVendor advisory
  55. 2026-08-09 20:52 UTCVendor advisory
  56. 2026-08-09 16:49 UTCEG score recompute
  57. 2026-08-09 16:49 UTCVendor advisory
  58. 2026-08-09 13:46 UTCEPSS rescore
  59. 2026-08-09 12:46 UTCVendor advisory
  60. 2026-08-09 08:04 UTCVendor advisory
  61. 2026-08-09 04:01 UTCEG score recompute
  62. 2026-08-09 04:01 UTCVendor advisory
  63. 2026-08-08 16:36 UTCEPSS rescore
  64. 2026-08-08 09:44 UTCVendor advisory
  65. 2026-08-08 05:41 UTCVendor advisory
  66. 2026-08-08 01:38 UTCVendor advisory
  67. 2026-08-07 21:35 UTCVendor advisory
  68. 2026-08-07 17:32 UTCEG score recompute
  69. 2026-08-07 17:32 UTCVendor advisory
  70. 2026-08-07 16:26 UTCEPSS rescore
  71. 2026-08-07 13:29 UTCVendor advisory
  72. 2026-08-06 21:33 UTCVendor advisory
  73. 2026-08-06 17:28 UTCEG score recompute
  74. 2026-08-06 17:28 UTCVendor advisory
  75. 2026-08-06 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-41118?
CVE-2025-41118 is a critical vulnerability published on April 15, 2026. 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…
When was CVE-2025-41118 disclosed?
CVE-2025-41118 was first published in the National Vulnerability Database on April 15, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-41118 actively exploited?
CVE-2025-41118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.8% of all scored CVEs.
What is the CVSS score of CVE-2025-41118?
CVE-2025-41118 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-41118?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-41118, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-41118

Explore →

Is Your Infrastructure Affected by CVE-2025-41118?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs