Loading story…
Grafana Alloy versions 1.0.0 through 1.18.1 are affected by CVE-2026-75889, a high-severity arbitrary local-file disclosure vulnerability (CVSS 7.7) in the prometheus.operator.servicemonitors component. An attacker able to create or modify a Kubernetes ServiceMonitor in a namespace monitored by Alloy can abuse bearerTokenFile to make Alloy read a local file and transmit its contents as a bearer token to an attacker-controlled scrape endpoint.
Files readable by the Alloy process—including its projected Kubernetes service-account token—may be exposed, potentially allowing an attacker to obtain Alloy’s Kubernetes permissions. Canadian and Guyanese cyber authorities also issued alerts for CVE-2026-19516 affecting Alloy 1.18.1 and earlier, urging administrators to review Grafana guidance and apply available updates or mitigations; the advisories did not state severity, technical impact, or active exploitation status.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The Canadian Centre for Cyber Security issued advisory AV26-860 for CVE-2026-19516 in Grafana Alloy, advising users and administrators to review Grafana resources and apply necessary updates when available.
Grafana Labs published CVE-2026-75889, a CVSS 7.7 high-severity arbitrary local-file disclosure flaw in Alloy's prometheus.operator.servicemonitors component. An attacker able to modify a ServiceMonitor in an Alloy-watched namespace could configure bearerTokenFile to exfiltrate files accessible to Alloy, potentially including its Kubernetes service-account token.
Grafana published a security advisory addressing CVE-2026-19516 in Grafana Alloy. The advisory identified Alloy version 1.18.1 and earlier as affected.
The Guyana National CIRT recommended that Grafana Alloy users and administrators review Grafana's CVE-2026-19516 advisory and apply necessary updates or mitigations.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cirt.gy
Open sourcemalware.news
Open sourcecyber.gc.ca
Open sourcecve.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Grafana issued urgent patches for two high-severity vulnerabilities, including **`CVE-2026-27876`**, a critical flaw in the SQL Expressions feature that can allow an attacker with **Viewer** privileges or higher to write arbitrary files to the server and potentially escalate to full **remote code execution**. The issue can be chained into broader compromise scenarios, including unauthorized SSH access, prompting public warnings from national defenders such as Belgium’s CCB to patch immediately. Grafana also fixed **`CVE-2026-27880`**, which affects OpenFeature validation endpoints and allows **unauthenticated** attackers to crash vulnerable instances by sending oversized requests that exhaust memory. Grafana Labs said patched releases, including **12.4.2**, are available and noted that **Amazon Managed Grafana** and **Azure Managed Grafana** were already protected under embargo; for temporary mitigation, administrators were advised to disable the `sqlExpressions` feature toggle and use highly available deployments and reverse proxies such as **Nginx** or **Cloudflare** to restrict request sizes.
Jun 29, 2026
A newly disclosed server-side request forgery flaw, **CVE-2026-19516**, affects **Grafana MCP Server** and **mcp-grafana** in versions **prior to or equal to `1.0.0`**. The vulnerability allows a caller-controlled `X-Grafana-URL` header to steer outbound requests to attacker-chosen destinations, while the `grafana_api_request` tool lets the caller select the HTTP method, path, and body. That combination can be abused to reach internal, loopback, and link-local services, including cloud metadata endpoints, and read back the responses. The issue remains exploitable despite an earlier fix for **CVE-2026-15583**, which prevented the configured Grafana service-account token from being sent to unintended destinations but did not restrict where requests could be sent. The **Canadian Centre for Cyber Security** issued advisory **AV26-796**, warning that Grafana products are affected and urging administrators to review vendor guidance and apply updates when available.
Aug 14, 2026
Grafana published security advisories for two products, including **CVE-2026-15583** in **Grafana MCP Server** and a separate unbounded memory allocation issue in **Grafana Loki**. The MCP Server flaw affects version `0.17.1` and earlier and stems from a confused-deputy **SSRF** condition triggered through the `X-Grafana-URL` header. An unauthenticated remote attacker can use the bug to exfiltrate the server’s environment-configured Grafana service-account token and force requests to arbitrary internal services. The SSRF exposure also extends to sensitive internal targets such as cloud metadata endpoints, raising the risk of credential theft and internal network access without user interaction. Grafana’s Loki advisory covers version `3.7.0` and earlier, where detected_fields query limits can cause unbounded memory allocation. Government and security notices have urged administrators to review Grafana’s advisories and apply the vendor’s updates for affected MCP Server and Loki deployments.
Jul 16, 2026