Answer in brief
CVE-2026-110337 records a Medium severity (CVSS 4.1) vulnerability in CVE-2026-110337 CVE Record. The current sources do not mark it as known exploited. The current feed maps Grafana/Strava Datasource (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Grafana/Strava Datasource (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Grafana/Strava Datasourcegeneric | >=1.2.0 <=1.7.2 | Not reported |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 19, 2026
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 source text, attributed separately from HOL analysis.