CVE-2026-110337: Grafana Strava Datasource · CVE Record
Affects Grafana Strava DatasourceSource CVE Database V5
Not known to be exploited · CVSS 4.1 Medium.
Data as of 19 Nov 2026, 12:51 UTC
Thin evidence
One scorer or none| CNA (GRAFANA) | CVSS 3.1 | 4.1 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GrafanaStrava Datasource | Affected
| Fixed in– |
AI-suggested
A fix restricting allowed Strava API endpoints to a fixed set of five patterns and rejecting invalid paths is pending release. Until the patch is available, administrators should consider limiting Viewer access or the use of the Strava Datasource plugin. Since the plugin is not a cloud service, remediation requires updating to the fixed plugin version once released. Monitor the vendor's advisory for the official patch release and apply it promptly to prevent unauthorized data access.
Description
CVE-2026-110337 is a vulnerability in the Grafana Strava Datasource plugin versions 1.2.0 through 1.7.2. The plugin's resource handler forwards a client-supplied endpoint string and query parameters to the Strava API without validating the endpoint path. This allows any user with Viewer permissions, who have the datasources:query permission by default, to make read-only GET requests to any Strava API path permitted by the connected account's OAuth token. The plugin frontend only requires a fixed set of five endpoint patterns, but the lack of validation allows broader access. A fix restricting allowed endpoints to these five patterns is pending release.