S3 SSE-C Encryption Key Exposed in Plaintext via Config Endpoint (CVE-2025-41118 Pattern)
cve-program · CVE-2026-28377
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2026-16424
PublishedA 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.
Read the publisher's advisorynvd · CVE-2026-28377
PublishedA 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.
Read the publisher's advisoryosv · GHSA-ffqx-q65f-36jf
PublishedA 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.
Read the publisher's advisoryosv · GO-2026-5359
PublishedGrafana Tempo has Inadequate Encryption Strength in github.com/grafana/tempo. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/grafana/tempo before v2.10.3.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-28377 · CVE overview and exploitation status
cve-program · CVE-2026-28377
euvd · EUVD-2026-16424
nvd · CVE-2026-28377
osv · GHSA-ffqx-q65f-36jf
- https://nvd.nist.gov/vuln/detail/CVE-2026-28377
- https://github.com/grafana/tempo/commit/bb8ca663db34a0980c9758b40d918fda3b4dbec3
- https://github.com/advisories/GHSA-ffqx-q65f-36jf
- https://github.com/grafana/tempo
- https://github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/CHANGELOG.md?plain=1#L135
- https://grafana.com/security/security-advisories/cve-2026-28377
osv · GO-2026-5359
- https://github.com/advisories/GHSA-ffqx-q65f-36jf
- https://nvd.nist.gov/vuln/detail/CVE-2026-28377
- https://github.com/grafana/tempo/commit/bb8ca663db34a0980c9758b40d918fda3b4dbec3
- https://github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/CHANGELOG.md?plain=1#L135
- https://grafana.com/security/security-advisories/cve-2026-28377
Related changes
Linked by CVE identifierNo related changes are available here.