Security readout for executives and security teams
Plain-English summary
CVE-2026-42127 lets an unauthenticated attacker overload affected Grafana public dashboard query processing with very large JSON request bodies. The expected impact is service disruption from memory exhaustion, not data theft or data modification. Publicly reachable Grafana instances using affected versions should be prioritized for review.
Executive priority
Treat as high priority for externally reachable Grafana. The issue can take dashboards offline without credentials, affecting monitoring visibility and operational response. Prioritize public or partner-facing deployments first; internal-only systems still need review based on trust boundaries.
Technical view
The public dashboard query endpoint processes request bodies without limiting size first. An attacker with network access can send oversized JSON and trigger excessive memory allocation. CVSS is 7.5: network exploitable, low complexity, no privileges, no user interaction, availability impact only. Listed products are Grafana OSS and Grafana Enterprise versions 11.6.0, 12.2.0, 12.3.0, 12.4.0, and 13.0.0.
Likely exposure
Exposure is most likely where Grafana OSS or Enterprise listed versions are internet-accessible or otherwise reachable by untrusted users and public dashboard query functionality is available. No authentication or valid dashboard access token is required according to the source bundle.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation is described as unauthenticated denial of service by memory exhaustion through arbitrarily large JSON request bodies. No confidentiality or integrity impact is identified.
Researcher notes
Evidence is limited to the CVE record and Grafana advisory reference in the provided bundle. No fixed versions, patch details, endpoint path, or exploitation-in-the-wild evidence are included here. The listed affected versions and default status should be reconciled against the vendor advisory during triage.
Mitigation direction
- Review Grafana’s advisory for affected and fixed version guidance.
- Upgrade or apply vendor-provided remediation if Grafana publishes it.
- Restrict untrusted network access to public dashboard query functionality where feasible.
- Apply request body size limits at perimeter controls where supported.
- Monitor Grafana memory usage and availability until remediation is complete.
Validation and detection
- Inventory Grafana OSS and Enterprise versions in use.
- Identify instances running listed affected versions.
- Check whether public dashboard query functionality is reachable by untrusted networks.
- Review logs for unusually large unauthenticated dashboard query requests.
- Correlate memory spikes or restarts with public dashboard traffic.
Public sources used
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-400: 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 lookupCWE-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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-42127 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:N/I:N/A:H3.93.6GRAFANAVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/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-42127CVE 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.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.