CVE-2026-110337
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.
Properties
- Severity
- LOW
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00192
- Cvss severity
- LOW
- Cvss score
- 3.5
- Retrieved at
- 2026-11-22T12:32:25+00:00
- Last source
- FIRST EPSS
- Score
- 3.5
- Cvss version
- 3.1
- Cve id
- CVE-2026-110337
- Cvss vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
- First seen by Signal
- 2026-11-19T15:26:52+00:00
- Name
- CVE-2026-110337
- Vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
- Published at
- 2026-11-19T13:17:26.427
- Last modified
- 2026-11-19T17:17:52.907
- Epss percentile
- 0.08816
Related Entities (1)
HAS_WEAKNESS (1)
Related research
Explore deeper with Ninja Signal's threat intelligence graph