Security readout for executives and security teams
Plain-English summary
An authenticated Grafana user can send a request that makes the server load an entire request body into memory. A sufficiently large request could exhaust available memory and interrupt Grafana service. The issue affects availability, not data confidentiality or integrity, according to the supplied CVSS assessment.
Executive priority
Prioritize remediation on internet-reachable, business-critical, or broadly shared Grafana instances. Although rated medium and requiring authentication, successful abuse can make monitoring dashboards unavailable. Address during the normal vulnerability cycle, escalating where Grafana availability supports incident response or essential operations.
Technical view
The Grafana plugin resources endpoint reads the complete request body without a bounded allocation, creating CWE-770 resource exhaustion. Exploitation is network-accessible, requires low privileges, has low complexity, and needs no user interaction. An out-of-memory condition can cause denial of service. CVSS 3.1 is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Likely exposure
Exposure exists where an affected Grafana OSS version is reachable by authenticated, low-privilege users. The bundle identifies versions 6.7.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. It marks other versions unaffected by default; deployment-specific controls remain relevant.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not identified as being in KEV. Abuse requires authentication but no user interaction. The primary risk is service disruption through memory exhaustion, particularly where untrusted or broadly provisioned users can access affected Grafana instances.
Researcher notes
The weakness is CWE-770: allocation of resources without limits or throttling. The vulnerable behavior is complete request-body buffering at the plugin resources endpoint. The supplied evidence supports availability impact only. It does not provide fixed-version details, affected configuration nuances, proof-of-concept information, or evidence of exploitation in the wild.
Mitigation direction
- Review Grafana's advisory and upgrade to a vendor-identified fixed release; the supplied bundle does not name one.
- Restrict Grafana access to trusted users and apply least-privilege permissions while remediation is pending.
- Consider bounded request-body limits at an upstream proxy, validating compatibility before production rollout.
- Ensure memory limits, monitoring, and recovery procedures can contain an out-of-memory event.
Validation and detection
- Inventory Grafana OSS deployments and compare versions against the exact affected versions in the supplied record.
- Confirm which authenticated roles can reach plugin resource functionality without sending oversized requests.
- Review proxy and application controls for enforced request-body size limits.
- Monitor memory utilization, restarts, and logs for unusual authenticated requests involving plugin resources.
- After remediation, verify the deployed release against Grafana's advisory and repeat safe access-control checks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2026-28383 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6GRAFANAVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://grafana.com/security/security-advisories/cve-2026-28383CVE reference, GRAFANA · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.