CVE-2026-28376: Grafana Live push endpoint allows unbounded memory allocation leading to OOM
The Grafana Live push endpoint can be exploited to cause unbounded memory allocation by sending a large or streaming request body, potentially leading to out-of-memory conditions. An authenticated user with access to the Grafana Live API can trigger this issue.
Security readout for executives and security teams
Plain-English summary
An authenticated Grafana user with Live API access can submit an oversized or streaming request that continually consumes memory. This may exhaust server memory and interrupt dashboards, alerting, or monitoring operations. The supplied evidence indicates an availability impact, not data theft or modification.
Executive priority
Schedule near-term remediation, prioritizing Grafana instances supporting security monitoring, alerting, or other operationally critical services. Escalate urgency where Live API access is broadly granted or exposed beyond trusted networks. Current evidence does not justify treating this as a critical or actively exploited vulnerability.
Technical view
CVE-2026-28376 is a CWE-770 resource-allocation flaw in the Grafana Live push endpoint. Request bodies can cause unbounded memory allocation, potentially terminating Grafana through an out-of-memory condition. CVSS 3.1 is 6.5: network-accessible, low complexity, low privileges, no user interaction, with high availability impact.
Likely exposure
Exposure requires an affected Grafana OSS version, network reachability to the Grafana Live API, and an authenticated account authorized to access it. Risk is greater where many users, contractors, or compromised accounts can reach Grafana. The supplied bundle identifies specific affected versions but does not describe configuration-dependent exceptions.
Exploitation context
The request can be initiated remotely by a low-privileged authenticated user and requires no victim interaction. The supplied sources do not establish public exploitation, exploit availability, or CISA KEV inclusion. Therefore, active exploitation should not be assumed.
Researcher notes
The supplied affected list names Grafana OSS 8.0.0, 11.6.14, 12.0.0, 12.2.8, 12.3.0, 12.3.6, 12.4.0, 12.4.3, 13.0.0, and 13.0.1, with other versions defaulting to unaffected. The bundle does not name fixed releases, request limits, configuration prerequisites, or detection indicators; consult the vendor advisory for those details.
Mitigation direction
Review Grafana’s advisory and apply the vendor-supported corrected release or mitigation it specifies.
Temporarily restrict Grafana Live API access to trusted users where operationally feasible.
Reduce unnecessary network exposure to Grafana while remediation is pending.
Monitor Grafana memory consumption, restarts, and out-of-memory events for suspicious patterns.
Validation and detection
Inventory Grafana OSS versions and compare them with the vendor advisory’s affected-version guidance.
Confirm which authenticated roles can reach the Grafana Live push endpoint without sending oversized requests.
Review proxy and application logs for unusually large, prolonged, or incomplete Live push requests.
Verify memory stability and absence of out-of-memory restarts after vendor remediation.
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 · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.