Security readout for executives and security teams
Plain-English summary
Grafana Tempo 2.10.3 can expose an S3 customer-provided encryption key in plaintext through its /status/config endpoint. If that endpoint is reachable by an unauthorized user, the key protecting trace data in S3 could be disclosed. The known impact is loss of confidentiality, not data modification or service outage.
Executive priority
Prioritize within the current remediation cycle if Tempo 2.10.3 uses S3 SSE-C. Escalate faster if the status endpoint is internet-facing or shared across untrusted networks.
Technical view
The source describes a network-reachable, unauthenticated confidentiality issue in Tempo 2.10.3. The /status/config endpoint may reveal the S3 SSE-C encryption key in plaintext. CVSS 3.1 is 7.5 with high confidentiality impact and no stated integrity or availability impact. No fixed version is provided in the supplied sources.
Likely exposure
Organizations running Grafana Tempo 2.10.3 with S3 SSE-C configured are the relevant exposure group. Risk is highest where /status/config is reachable without strong access controls.
Exploitation context
The CVE record does not indicate KEV listing or active exploitation. The provided evidence supports unauthenticated network exposure of sensitive configuration, but does not provide public exploit evidence or attacker activity.
Researcher notes
Evidence is limited to the CVE bundle and Grafana advisory reference. The issue matches a sensitive-configuration-disclosure pattern: secret material appears in an operational config endpoint. Confirm behavior only in authorized environments and avoid retaining exposed key material.
Mitigation direction
- Review the Grafana advisory for official fixed versions or supported workarounds.
- Restrict access to Tempo status and configuration endpoints to trusted administrative networks.
- Treat exposed S3 SSE-C keys as compromised and rotate them after containment.
- Review S3 trace data access controls and least-privilege permissions.
- Upgrade Tempo when Grafana identifies a corrected release.
Validation and detection
- Inventory Grafana Tempo deployments and identify any running version 2.10.3.
- Confirm whether S3 SSE-C is configured for trace storage.
- Verify /status/config is not publicly or broadly reachable.
- Check controlled endpoint output for plaintext sensitive S3 key material.
- Review access logs for unexpected /status/config requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-326: 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.
Open ATT&CK lookupCVE-2026-28377 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GRAFANAVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://grafana.com/security/security-advisories/cve-2026-28377CVE reference, GRAFANA · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inadequate Encryption Strength
Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.