CVE-2021-39226

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-08-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2021-2169 (ENISA EUVD) · GHSA-69j6-29vr-p3j9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 99.9%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Grafana is an open source data visualization platform. In affected versions unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths: /dashboard/snapshot/:key, or /api/snapshots/:key. If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path: /api/snapshots-delete/:deleteKey. Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths: /api/snapshots/:key, or /api/snapshots-delete/:deleteKey. The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss. This issue has been resolved in versions 8.1.6 and 7.5.11. If for some reason you cannot upgrade you can use a reverse proxy or similar to block access to the literal paths: /api/snapshots/:key, /api/snapshots-delete/:deleteKey, /dashboard/snapshot/:key, and /api/snapshots/:key. They have no normal function and can be disabled without side effects.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage 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)Attend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://grafana.com/blog/2021/10/05/grafana-7.5.11-and-8.1.6-released-with-critical-security-fix/ · https://nvd.nist.gov/vuln/detail/CVE-2021-39226

Published

October 5, 2021

Last Modified

October 24, 2025

Advisory Details (8)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: github_commit, github.
GitHub commit

commit 2d456a637585 (grafana/grafana)

Fix landed in grafana/grafana commit 2d456a637585 — awaiting tagged release

https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269
Web page

oss-security - CVE-2021-39226 Grafana snapshot authentication bypass

http://www.openwall.com/lists/oss-security/2021/10/05/4
Web page

[SECURITY] Fedora 34 Update: grafana-7.5.11-1.fc34 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E6ANHRDBXQT6TURLP2THM26ZPDINFBEG/
Web page

[SECURITY] Fedora 35 Update: grafana-7.5.11-1.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DCKBFUSY6V4VU5AQUYWKISREZX5NLQJT/
Web page

What's new in Grafana | Grafana documentation

https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/
Web page

What's new in Grafana | Grafana documentation

https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/
GitHub advisoryMentions a patch (unverified)

CVE-2021-39226 Snapshot authentication bypass · Advisory · grafana/grafana · GitHub

https://github.com/grafana/grafana/security/advisories/GHSA-69j6-29vr-p3j9

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-grafana:v4.8.0-202208311019.p0.gf98b47f.assembly.stream2022-09-14redhat
redhatopenshift4/ose-grafana:v4.7.0-202208310205.p0.g613acad.assembly.stream2022-09-13redhat
redhatopenshift4/ose-grafana:v4.9.0-202208311003.p0.g3b7bed6.assembly.stream2022-09-12redhat
redhatopenshift4/ose-grafana:v4.6.0-202208310224.p0.gcf170c0.assembly.stream2022-09-09redhat
redhatopenshift3/grafana:v3.11.784-1.g423963f2022-09-07redhat
redhatopenshift4/ose-grafana:v4.10.0-202202160023.p0.g48aec35.assembly.stream2022-03-10redhat
redhatgrafana-0:6.2.2-7.el8_12021-10-12redhat
redhatgrafana-0:6.3.6-3.el8_22021-10-12redhat
redhatgrafana-0:7.3.6-3.el8_42021-10-12redhat
gogithub.com/grafana/grafana @ 7.5.11 (fixes < 7.5.11)—ghsa
gogithub.com/grafana/grafana @ 8.1.6 (fixes >= 8.0.0, < 8.1.6)—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)
PackageVulnerable rangeFix by version rangeDependents
github.com/grafana/grafana—
  • every version up to 7.5.11: fixed in 7.5.11
  • 8.0.0 up to 8.1.6: fixed in 8.1.6
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 17× in last 7d / 102× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 945 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 845 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 23:08 UTCEG score recompute
  2. 2026-11-01 23:08 UTCVendor advisory
  3. 2026-11-01 23:08 UTCGHSA enrichmentGHSA-69j6-29vr-p3j9 · GitHub severity HIGH · GitHub CVSS 7.3
  4. 2026-11-01 08:31 UTCGHSA enrichmentGHSA-69j6-29vr-p3j9 · GitHub severity HIGH · GitHub CVSS 7.3
  5. 2026-11-01 08:31 UTCEG score recompute
  6. 2026-10-31 22:16 UTCEG score recompute
  7. 2026-10-31 22:16 UTCVendor advisory
  8. 2026-10-30 21:21 UTCEG score recompute
  9. 2026-10-30 21:21 UTCVendor advisory
  10. 2026-10-29 20:30 UTCEG score recompute
  11. 2026-10-29 20:30 UTCVendor advisory
  12. 2026-10-28 19:38 UTCEG score recompute
  13. 2026-10-28 19:38 UTCVendor advisory
  14. 2026-10-27 18:47 UTCEG score recompute
  15. 2026-10-27 18:47 UTCVendor advisory
  16. 2026-10-26 17:55 UTCEG score recompute
  17. 2026-10-26 17:55 UTCVendor advisory
  18. 2026-10-25 17:03 UTCEG score recompute
  19. 2026-10-25 17:03 UTCVendor advisory
  20. 2026-10-25 16:28 UTCEPSS rescoreEPSS 99.9% · 99th percentile
  21. 2026-10-24 16:12 UTCEG score recompute
  22. 2026-10-24 16:12 UTCVendor advisory
  23. 2026-10-23 15:15 UTCEG score recompute
  24. 2026-10-23 15:15 UTCVendor advisory
  25. 2026-10-22 14:22 UTCEG score recompute
Show 75 more
  1. 2026-10-22 14:22 UTCVendor advisory
  2. 2026-10-21 13:29 UTCEG score recompute
  3. 2026-10-21 13:29 UTCVendor advisory
  4. 2026-10-20 12:38 UTCEG score recompute
  5. 2026-10-20 12:38 UTCVendor advisory
  6. 2026-10-19 11:45 UTCEG score recompute
  7. 2026-10-19 11:45 UTCVendor advisory
  8. 2026-10-18 10:51 UTCVendor advisory
  9. 2026-10-18 08:55 UTCEG score recompute
  10. 2026-10-17 09:58 UTCEG score recompute
  11. 2026-10-17 09:58 UTCVendor advisory
  12. 2026-10-16 16:34 UTCEPSS rescoreEPSS 99.9% · 99th percentile
  13. 2026-10-16 09:05 UTCEG score recompute
  14. 2026-10-16 09:05 UTCVendor advisory
  15. 2026-10-15 08:14 UTCEG score recompute
  16. 2026-10-15 08:14 UTCVendor advisory
  17. 2026-10-14 07:20 UTCEG score recompute
  18. 2026-10-14 07:20 UTCVendor advisory
  19. 2026-10-13 06:26 UTCVendor advisory
  20. 2026-10-12 19:11 UTCEG score recompute
  21. 2026-10-12 05:33 UTCVendor advisory
  22. 2026-10-12 01:35 UTCVendor advisory
  23. 2026-10-11 21:41 UTCEG score recompute
  24. 2026-10-11 21:41 UTCVendor advisory
  25. 2026-10-11 17:48 UTCEG score recompute
  26. 2026-10-11 17:48 UTCVendor advisory
  27. 2026-10-11 13:52 UTCEG score recompute
  28. 2026-10-11 13:52 UTCVendor advisory
  29. 2026-10-11 09:57 UTCVendor advisory
  30. 2026-10-11 06:02 UTCVendor advisory
  31. 2026-10-11 02:08 UTCVendor advisory
  32. 2026-10-10 22:12 UTCVendor advisory
  33. 2026-10-10 18:16 UTCVendor advisory
  34. 2026-10-10 14:21 UTCVendor advisory
  35. 2026-10-10 10:27 UTCVendor advisory
  36. 2026-10-10 06:32 UTCVendor advisory
  37. 2026-10-10 02:38 UTCVendor advisory
  38. 2026-10-09 22:44 UTCVendor advisory
  39. 2026-10-09 18:50 UTCVendor advisory
  40. 2026-10-09 14:56 UTCVendor advisory
  41. 2026-10-09 11:01 UTCVendor advisory
  42. 2026-10-09 07:07 UTCVendor advisory
  43. 2026-10-09 03:13 UTCVendor advisory
  44. 2026-10-08 23:19 UTCVendor advisory
  45. 2026-10-08 19:25 UTCVendor advisory
  46. 2026-10-08 15:31 UTCVendor advisory
  47. 2026-10-08 11:37 UTCVendor advisory
  48. 2026-10-08 07:43 UTCVendor advisory
  49. 2026-10-08 03:49 UTCVendor advisory
  50. 2026-10-07 23:55 UTCVendor advisory
  51. 2026-10-07 20:00 UTCVendor advisory
  52. 2026-10-07 16:06 UTCVendor advisory
  53. 2026-10-07 12:12 UTCVendor advisory
  54. 2026-10-07 08:19 UTCVendor advisory
  55. 2026-10-07 04:22 UTCVendor advisory
  56. 2026-10-07 00:28 UTCVendor advisory
  57. 2026-10-06 20:30 UTCVendor advisory
  58. 2026-10-06 16:37 UTCVendor advisory
  59. 2026-10-06 12:42 UTCVendor advisory
  60. 2026-10-06 08:48 UTCVendor advisory
  61. 2026-10-06 04:55 UTCVendor advisory
  62. 2026-10-06 01:00 UTCVendor advisory
  63. 2026-10-05 21:05 UTCVendor advisory
  64. 2026-10-05 17:11 UTCVendor advisory
  65. 2026-10-05 13:18 UTCVendor advisory
  66. 2026-10-05 09:24 UTCVendor advisory
  67. 2026-10-05 05:30 UTCVendor advisory
  68. 2026-10-05 01:36 UTCVendor advisory
  69. 2026-10-04 21:42 UTCVendor advisory
  70. 2026-10-04 17:48 UTCVendor advisory
  71. 2026-10-04 13:52 UTCVendor advisory
  72. 2026-10-04 09:58 UTCVendor advisory
  73. 2026-10-04 06:04 UTCVendor advisory
  74. 2026-10-04 02:10 UTCVendor advisory
  75. 2026-10-03 22:16 UTCVendor advisory

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-39226.yaml
    Published Dec 1, 2021

    Grafana Snapshot - Authentication Bypass

    Open source ↗

Frequently asked(6)

What is CVE-2021-39226?
CVE-2021-39226 is a critical-severity vulnerability; its CVE record was published on October 5, 2021. Grafana is an open source data visualization platform. In affected versions unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths: /dashboard/snapshot/:key, or /api/snapshots/:key. If the snapshot "public_mode"…
When was the CVE record for CVE-2021-39226 published?
The CVE record for CVE-2021-39226 was published on October 5, 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 October 24, 2025; the record at its source may have been updated since.
Is CVE-2021-39226 actively exploited?
Yes. CISA added CVE-2021-39226 to the Known Exploited Vulnerabilities catalog on August 25, 2022, affecting Grafana Labs Grafana. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-39226?
CVE-2021-39226 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2021-39226?
CVE-2021-39226 affects Grafana Labs Grafana. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2021-39226?
A fix for CVE-2021-39226 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-39226 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-39226

Explore →

Is Your Infrastructure Affected by CVE-2021-39226?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.