Grafana · Grafana · published 2026-01-27
CVE-2026-21720Unauthenticated DoS: avatar cache leaks goroutines when /avatar/:hash requests time out
Routine No exploitation evidence; EPSS 0.7%.
CVE-2026-21720 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 53% of all CVEs. This Grafana vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
ObservabilityGrafana
Grafana security fixes: 3 CVEs
Why: Vendor security release for server software (most severe: CVE-2026-21721).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (54th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Grafana grafana/grafana-enterprise
3.0.0to before11.6.9(affected)
- Grafana grafana/grafana-enterprise
3.0.0to before12.0.8(affected)
- Grafana grafana/grafana-enterprise
3.0.0to before12.1.5(affected)
- Grafana grafana/grafana
3.0.0to before11.6.9(affected)
- Grafana grafana/grafana
3.0.0to before12.0.8(affected)
- Grafana grafana/grafana
3.0.0to before12.1.5(affected)
- Grafana grafana/grafana-enterprise
3.0.0to before12.2.3(affected)
- Grafana grafana/grafana
3.0.0to before12.2.3(affected)
- Grafana grafana/grafana-enterprise
3.0.0to before12.3.1(affected)
- Grafana grafana/grafana
3.0.0to before12.3.1(affected)
Description (from the CVE record)#
Every uncached /avatar/:hash request spawns a goroutine that refreshes the Gravatar image. If the refresh sits in the 10-slot worker queue longer than three seconds, the handler times out and stops listening for the result, so that goroutine blocks forever trying to send on an unbuffered channel. Sustained traffic with random hashes keeps tripping this timeout, so goroutine count grows linearly, eventually exhausting memory and causing Grafana to crash on some systems.
Quoted from the CVE Program record.