Skip to main content
Menu
CVEs

Grafana Strava Datasource authorization bypass in resource endpoint

CVE-2026-110337EUVD-2026-129919GHSA-5FMG-W26P-CJVPPublished November 19, 2026, updated

4.1MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

A flaw in Grafana's Strava Datasource plugin lets a remote user with low privileges, such as a Viewer, read data from any Strava API path the connected account can access. The attacker sends requests over the network to the plugin's resource endpoint without any user action, and the requests use the access token stored on the datasource rather than the caller's own identity. The attack is read-only.

Written by a model

Original 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 (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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110337 (CVE-2026-110337 CVE Record), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110337 (entry last updated 2026-11-19):
Affected:
- Grafana Strava Datasource: from 1.2.0, through 1.7.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110337 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110337 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://grafana.com/security/security-advisories/cve-2026-110337
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110337
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110337"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.1/10CVSS 4.1
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorygrafana.com · security/security-advisories/cve-2026-110337
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-110337
RecordNVD · CVE-2026-110337

Questions about CVE-2026-110337

Is CVE-2026-110337 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-110337?

Strava Datasource: from 1.2.0 through 1.7.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.