Skip to content
Threat Brief

← All advisories

CVE-2026-110337

Medium 4.1No known exploitationFix status unknown

CVE-2026-110337 CVE Record

Record last updated

CVSS score

4.1

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 9% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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/ ) 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.

Weakness: CWE-863

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
None documented
Vendor guidance
grafana.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
GrafanaStrava Datasourcefrom 1.2.0 up to and including 1.7.2Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GRAFANA

    Source: CVE Program (opens in a new tab)

Vendor guidance and references