CVE-2026-21720: Unauthenticated DoS: avatar cache leaks goroutines when /avatar/:hash requests time out
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.
Security readout for executives and security teams
Plain-English summary
This is an unauthenticated availability flaw in Grafana’s avatar handling. Repeated uncached avatar requests can leave background work stuck, steadily consuming memory until Grafana may crash. The bundle rates impact as high because no login or user interaction is required and the result is service disruption, not data theft.
Executive priority
Prioritize externally exposed Grafana services because the issue can crash monitoring dashboards without authentication. Treat this as an availability risk requiring prompt vendor-version confirmation and remediation planning.
Technical view
For uncached /avatar/:hash requests, Grafana starts a refresh goroutine. If queued work exceeds the three-second handler timeout, the handler stops receiving while the goroutine later sends on an unbuffered channel, blocking permanently. Sustained random hashes can grow goroutines linearly and exhaust memory.
Likely exposure
Most concern is for Grafana or Grafana Enterprise instances reachable by untrusted users, especially internet-facing deployments. The provided affected metadata is duplicated and internally limited, so exact version exposure should be confirmed against Grafana’s advisory and Red Hat status.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires sustained unauthenticated request volume to the avatar endpoint, causing resource exhaustion rather than confidentiality or integrity compromise.
Researcher notes
Evidence supports a goroutine leak caused by timeout handling around avatar refresh results. The bundle does not provide a specific fixed version, patch commit, or confirmed exploitation. Affected-version data appears repetitive and should not be treated as complete without vendor confirmation.
Mitigation direction
Check Grafana’s advisory for affected and fixed versions before changing production systems.
Apply the vendor-recommended update or mitigation once confirmed for your deployment.
Reduce untrusted access to public Grafana endpoints where business requirements allow.
Monitor memory and goroutine growth; restart degraded instances as an operational recovery measure.
Validation and detection
Inventory Grafana OSS and Enterprise instances, including externally reachable deployments.
Compare installed versions against Grafana’s advisory and Red Hat CVE/VEX records.
Review access logs for unusual volume of randomized avatar requests and timeout patterns.
Check runtime telemetry for sustained goroutine growth or memory pressure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
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.
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.
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.
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.
We 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.