Skip to main content
CVE-2025-22874VulnerabilityPublished Updated

Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.7.0 release

Affects Red HatSource GCVE Database

0
Compare
Authoritative record:CVE-2025-22874· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 19:18 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Gogithub.com/golang/go/src/crypto/x509pkg:golang/github.com/golang/go/src/crypto/x509Other threatsAffected
  • =1.24.0-0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the Red Hat OpenShift distributed tracing platform (Tempo) 3.7.0 update as per Red Hat's official guidance to remediate CVE-2025-22874. The update includes network policies restricting API access, which mitigates the vulnerability. For the known Jaeger UI issue causing Tempo query pod failures, use the distributed tracing UI plugin as a workaround. No additional immediate actions are required beyond applying the update.

Description

Red Hat OpenShift distributed tracing platform (Tempo) 3.7.0 release includes security improvements and bug fixes addressing CVE-2025-22874. This update introduces a network policy for the Tempo Operator to restrict API access. A known issue affects the Jaeger UI causing Tempo query pod failures under certain actions, with a recommended workaround using the distributed tracing UI plugin.

References

Community reviews

Loading reviews…