Grafana · Grafana · published 2026-11-19
CVE-2026-110337CVE-2026-110337 CVE Record
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-110337 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 8% of all CVEs. This Grafana vulnerability: CVSS 4.1 (v3.1). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
ObservabilityGrafana
Grafana: Strava datasource can be used to access arbitrary resource
Why: Vendor security release for server software (most severe: CVE-2026-110337).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (9th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.1 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Grafana Strava Datasource
1.2.0through1.7.2(affected)
Description (from the CVE record)#
The Strava datasource plugin's resource handler POST /strava-api forwards a client-supplied endpoint string, and its query parameters, to the Strava API (https://www.strava.com/api/v3/<endpoint>) without validation. When the datasource is not in OAuth pass-through mode, the request is made with the access token stored on the datasource, not the caller's identity. Grafana authorises plugin resource calls only on the datasources:query permission, which Viewers have by default. Any such caller could therefore request any Strava API path the connected account's OAuth grant allows, for example athlete/clubs or routes/{id}, and read the response. The plugin's frontend (stravaApi.ts) only needs a fixed set of paths: athlete, athlete/activities, activities/{id}, activities/{id}/streams and segments/{id}. Requests to Strava are GET only, so the issue is read-only. Affected: plugin versions 1.2.0 through 1.7.2. The fix restricts endpoint to those five patterns and is pending release. The check runs before the access token is resolved, so a rejected request never causes a token refresh or any call to Strava. Paths with .. segments are rejected as well.
Quoted from the CVE Program record.