Skip to main content
Mallory
HighVulnerability

CVE-2026-42129: Path Traversal in Grafana Loki Data Source Plugin

Published Jun 22, 2026 · Updated 29 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.7High · v3.1
EPSS0.44%39th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Grafana Labs
IdentifiersCVE-2026-42129CWE-22 · Improper Limitation of a Pathname…

CVE-2026-42129 is a path-traversal vulnerability in the callResource handler of Grafana's Loki data source plugin. An authenticated user with Viewer permissions can escape the plugin's resource sandbox and access administrative Loki endpoints, exposing sensitive backend configuration and internal service information.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation breaches the authorization boundary between Grafana Viewer access and administrative Loki resources, resulting in sensitive backend configuration and internal service information disclosure. The CVSS v3.0 assessment assigns high confidentiality impact and no integrity or availability impact, with a base score of 7.7.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is applied, restrict Viewer access to affected Grafana instances and limit which users can interact with the Loki datasource plugin. Where possible, prevent Grafana from reaching Loki administrative endpoints such as /config, /services, and /ready through network-layer controls, reverse-proxy filtering, or backend access policy restrictions. Monitor for suspicious requests to plugin resource paths and unexpected access to Loki administrative endpoints.

Remediation

Patch, then assume compromise.

Upgrade the affected github.com/grafana/grafana Go package and related affected packages to version 1.9.2-0.20260616075434-82ef13993059 or later, where applicable. Deploy the relevant Grafana security updates after testing. Fixed Grafana application release versions are not specified.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Grafana LabsLoki Datasourceapplication
FAQ

Frequently asked questions

Is CVE-2026-42129 exploited in the wild?
As of Oct 19, 2026, Mallory has no reports of CVE-2026-42129 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-42129?
As of Oct 19, 2026, Mallory has found no public exploit for CVE-2026-42129.
Is there a patch for CVE-2026-42129?
Upgrade the affected github.com/grafana/grafana Go package and related affected packages to version 1.9.2-0.20260616075434-82ef13993059 or later, where applicable. Deploy the relevant Grafana security updates after testing.
What products are affected by CVE-2026-42129?
Grafana Labs Loki Datasource.
How severe is CVE-2026-42129?
CVE-2026-42129 has a CVSS v3.1 score of 7.7 (High) and an EPSS score of 0.44% (39th percentile) as of Oct 19, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.