The snapshot feature in Grafana 6.7.3 through 7.4.1 can allow an unauthenticated remote attackers to trigger a Denial of Service via a remote API call if a commonly used configuration is set.
CVE-2021-27358
HIGHNVD 7.58.9ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: EPSS in the top 5%, EPSS 50% or more.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.9 because EPSS predicted 83% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Also known asEUVD-2022-1033 (ENISA EUVD) · GHSA-h5rh-w6vm-9ghc (GitHub Security Advisories)Source: ENISA EUVD
8.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS PROB: 83%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 8.9HIGHhigh confidence
- EG Risk
- 67EG Risk 67/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation83% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 83%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 83% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
March 18, 2021
Last Modified
November 21, 2024
Advisory Details (4)
Auto-updated Nov 4, 2026Patch available.
Web page
What's new in Grafana | Grafana documentation
https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-4-2/Web page
grafana/CHANGELOG.md at main · grafana/grafana · GitHub
https://github.com/grafana/grafana/blob/master/CHANGELOG.md#742-2021-02-17Web page
grafana/CHANGELOG.md at main · grafana/grafana · GitHub
https://github.com/grafana/grafana/blob/master/CHANGELOG.mdVendor Advisories for CVE-2021-27358(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | grafana-0:7.5.9-4.el8 | 2021-11-09 | redhat |
| go | github.com/grafana/grafana @ 7.4.2 (fixes >= 6.7.3, < 7.4.2) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/grafana/grafana | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Public detection templates
(1 reference)A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.
- Nucleihttp/cves/2021/CVE-2021-27358.yamlPublished Dec 24, 2021
Grafana Unauthenticated Snapshot Creation
Open source ↗
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2021-27358?
CVE-2021-27358 is a high-severity vulnerability; its CVE record was published on March 18, 2021. The snapshot feature in Grafana 6.7.3 through 7.4.1 can allow an unauthenticated remote attackers to trigger a Denial of Service via a remote API call if a commonly used configuration is set.
When was the CVE record for CVE-2021-27358 published?
The CVE record for CVE-2021-27358 was published on March 18, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2021-27358 actively exploited?
CVE-2021-27358 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-27358?
CVE-2021-27358 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.9 (HIGH).
How do I remediate CVE-2021-27358?
A fix for CVE-2021-27358 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-27358 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-27358
Is Your Infrastructure Affected by CVE-2021-27358?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.