dbcve.org
TempoApplication · Grafana

CVE-2026-28377

HIGH · 7.5 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 2.10.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Grafana Tempo versions prior to the patch expose S3 SSE-C (Server-Side Encryption with Customer-Provided Keys) through the /status/config endpoint in plaintext. Any authenticated or unauthenticated user able to reach this endpoint can retrieve the encryption key used to protect trace data stored in Amazon S3, leading to confidentiality breach of stored data.

MitigationUpgrade Grafana Tempo to the patched version that filters sensitive configuration values from the /status/config endpoint, and rotate any SSE-C keys that may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TempoApplication
Affected:< 2.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Grafana Tempo version
    Query the /status endpoint or use the tempo --version command to identify the running version
    Affected if Version is prior to 2.10.3
  2. Verify S3 SSE-C configuration is in use
    Review Tempo configuration files or check the /status/config response for s3.sse.type set to customer-key
    Affected if S3 SSE-C (Server-Side Encryption with Customer-Provided Keys) is configured with a customer-managed key
  3. Confirm /status/config endpoint accessibility
    Make an HTTP GET request to the /status/config endpoint with appropriate network access
    Affected if The endpoint is reachable (with or without authentication) from your network
  4. Inspect endpoint response for exposed keys
    Review the JSON response from /status/config for plaintext values under s3.sse.key, s3.sse.key-id, or similar sensitive configuration fields
    Affected if The response contains unredacted SSE-C encryption keys or key IDs in plaintext

You are affected if running Grafana Tempo version below 2.10.3 with S3 SSE-C enabled and the /status/config endpoint is accessible, as plaintext keys can be retrieved from that endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.3 or later
Fixed in 2.10.3
Interim mitigation

Upgrade Grafana Tempo to the patched version that filters sensitive configuration values from the /status/config endpoint, and rotate any SSE-C keys that may have been exposed.

Recommended fix High confidence

Grafana Tempo 2.10.3 or latest stable release

  1. 1. Identify current Grafana Tempo version by querying the /api/v1/status/buildinfo endpoint or checking the deployment
  2. 2. Upgrade Grafana Tempo to version 2.10.3 or later (latest stable release recommended)
  3. 3. After upgrade, verify the S3 SSE-C key is no longer exposed by querying the /status/config endpoint and confirming the key is masked or not present
  4. 4. As a security precaution, rotate the exposed SSE-C encryption key since it may have been compromised
Caveat Review Tempo 2.10.x release notes for any configuration or storage changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tempo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28377 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data