Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-ffqx-q65f-36jf

Grafana Tempo has Inadequate Encryption Strength

CVSS 7.5 HighEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 27 Mar 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/grafana/tempoGo<2.10.32.10.3
Identifiers
GHSA-ffqx-q65f-36jf · CVE-2026-28377 · GO-2026-5359
Weakness (CWE)
CWE-326
Tags
Published
27 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grafana Tempo versions before 2.10.3 expose the S3 SSE-C encryption key in plaintext through the /status/config endpoint. An attacker who can reach that endpoint without authorization could obtain the key used to encrypt trace data stored in S3. Upgrade to Tempo 2.10.3 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GRAFANA)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.