CVE-2026-10601: Path traversal in the Tempo and Loki data source plugins
A user with Viewer permissions can use specially crafted requests to the Tempo and Loki data source plugins to reach unintended backend endpoints. Depending on the backend configuration this can expose data source credentials, leak internal responses, or trigger administrative actions on the configured backend.
Security readout for executives and security teams
Plain-English summary
CVE-2026-10601 is a medium-severity Grafana OSS issue in the Tempo and Loki data source plugins. A low-privileged Viewer user may send crafted requests that reach backend endpoints they should not access. Business impact depends on backend configuration and may include internal response leakage, credential exposure, or unintended backend actions.
Executive priority
Treat this as a moderate-priority authenticated exposure issue. It is not currently supported as actively exploited in the provided sources, but organizations using affected Grafana versions with Loki or Tempo should remediate promptly because backend configuration can raise business impact.
Technical view
The issue is classified as CWE-22 path traversal. In affected Grafana OSS versions, Tempo and Loki data source plugin request handling can allow a Viewer-authenticated user to access unintended backend endpoints. The CVSS 3.1 score is 5.4 with low attack complexity and required low privileges.
Likely exposure
Exposure is most likely where Grafana OSS 11.6.0, 12.2.0, 12.3.0, 12.4.0, or 13.0.0 is deployed with Tempo or Loki data sources configured and Viewer users present.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires authenticated Viewer permissions and specially crafted requests. Impact varies with the configured backend and what endpoints or credentials are reachable through the affected data source plugins.
Researcher notes
Evidence is limited to the CVE source bundle and Grafana advisory reference. The bundle names affected versions and impact categories but does not provide exploit details, fixed versions, or specific mitigations. Avoid assuming exposure unless Loki or Tempo data sources and Viewer-accessible users are present.
Mitigation direction
Check Grafana’s advisory for fixed versions or vendor-approved remediation.
Prioritize upgrading affected Grafana OSS versions once vendor guidance confirms the target release.
Limit Viewer access to Grafana instances using Loki or Tempo data sources.
Review Loki and Tempo backend permissions exposed to Grafana data source integrations.
Rotate exposed data source credentials if investigation suggests unauthorized backend access.
Validation and detection
Inventory Grafana OSS versions and compare against the affected version list.
Confirm whether Loki or Tempo data sources are configured on affected instances.
Review Grafana access logs for unusual data source plugin request patterns.
Assess backend configuration for sensitive administrative or credential-bearing endpoints.
Verify remediation by confirming Grafana version and data source access controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.