CVE-2026-81871: Tempo · OpenTelemetry-Go is the Go implementation of OpenTelemetry
Affects tempoSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.9.5-r3 when convenient.
Data as of 20 Nov 2026, 03:24 UTC
- Patch
- Available – fixed in 2.9.5-r3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade tempo to 2.9.5-r3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStarttempopkg:apk/cleanstart/tempoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to tempo version 2.9.5-r3 or later to remediate this vulnerability. Since a patch is available, applying the official fix is the recommended mitigation.
Description
A security vulnerability identified as CVE-2026-81871 affects the tempo package, which is the Go implementation of OpenTelemetry. The vulnerability impacts versions prior to 2.9.5-r3. A fix has been released in version 2.9.5-r3. The CVSS 4.0 base score is 6.3, indicating a medium severity level. There are no known exploits in the wild at this time.