CVE-2026-110337 in Strava Datasourceinfo

Summary

by MITRE • 11/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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability in the Strava datasource plugin for Grafana represents an insecure direct object reference and path traversal issue stemming from insufficient input validation on server-side API requests. Specifically, the resource handler endpoint POST /strava-api accepts a client-supplied string intended to represent the target API path along with associated query parameters. Instead of validating this input against a strict allowlist or sanitizing it for dangerous characters such as dot-dot sequences, the plugin directly concatenates this user-controlled value into the URL used to communicate with the external Strava API service at https://www.strava.com/api/v3/. This architectural flaw allows an attacker who can interact with the Grafana interface to dictate exactly which internal resource of the connected Strava account is accessed.

The operational impact of this vulnerability is significant due to the authentication model employed by Grafana plugins. When the datasource operates in non-OAuth pass-through mode, requests are authenticated using a single access token stored within the datasource configuration rather than the individual identity or permissions of the user making the request. Consequently, any Grafana user possessing the datasources:query permission can exploit this flaw. Since Viewers have this permission by default, even users with minimal privileges in the application can leverage their role to execute arbitrary read operations against the Strava API using the elevated credentials of the datasource owner. This effectively bypasses granular access controls and allows unauthorized data exfiltration from the connected account.

From a technical perspective, while the vulnerability is limited to GET requests, making it strictly read-only and preventing direct modification or deletion of external resources, it still poses severe privacy risks. An attacker can enumerate various endpoints such as athlete/clubs or routes/{id} provided they are within the scope of the OAuth grant held by the datasource owner. The plugin frontend code indicates that only a fixed set of paths—athlete, athlete/activities, activities/{id}, activities/{id}/streams, and segments/{id}—are legitimately required for normal operation. By allowing arbitrary path construction, the application exposes internal data structures and potentially sensitive personal information associated with the Strava account to any authenticated Grafana user.

This issue aligns with CWE-20 Improper Input Validation and CWE-611 Improper Restriction of XML External Entity or Path traversal concepts in web applications where dynamic URL construction occurs without adequate sanitization. In terms of attack vectors, it relates to ATT&CK techniques involving data exfiltration over alternative protocols if the API response is manipulated, though primarily here it facilitates unauthorized access to sensitive information via CWE-284 Improper Access Control. The lack of validation on path segments also opens potential for directory traversal attacks using dot-dot sequences, although the specific implementation details suggest the primary risk is logical rather than file-system based.

Mitigation strategies focus on implementing strict allowlisting mechanisms within the plugin codebase. Developers must restrict the endpoint parameter to only accept the predefined valid paths identified in the frontend logic: athlete, athlete/activities, activities/{id}, activities/{id}/streams, and segments/{id}. Additionally, input validation should explicitly reject any path containing suspicious sequences such as double dots or other characters that could facilitate traversal attacks. This check must be executed before resolving the access token to prevent unnecessary API calls or potential side effects like token refreshes for invalid requests. Users of affected plugin versions 1.2.0 through 1.7.2 should upgrade immediately once the patched version is released, and in the interim, administrators might consider restricting datasources:query permissions if feasible within their organizational security policies to limit exposure until the fix is deployed.

Responsible

GRAFANA

Reservation

10/13/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00192

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!