CVE-2026-48586VulnerabilityPublished 8 Sep 2026Updated 31 Oct 2026

Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.11.0 release

Affects Red HatSource GCVE Database

Compare

Authoritative record:CVE-2026-48586· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade Red Hat thrift to 0.24.0 soon.

Data as of 31 Oct 2026, 17:22 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.24.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jul 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache Thrift and github.com/apache/thrift and Apache Software Foundation/org.apache.thrift:libthrift to 0.24.0.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Thrift	Affected <0.24.0	Fixed in 0.24.0
Gogithub.com/apache/thrift`pkg:golang/github.com/apache/thrift`Other threats	Affected <0.24.0	Fixed in 0.24.0
MavenApache Software Foundation/org.apache.thrift:libthrift`pkg:maven/Apache Software Foundation/org.apache.thrift:libthrift`Other threats	Affected <0.24.0	Fixed in 0.24.0

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

Description

This release of the Red Hat build of OpenTelemetry provides new features, security improvements, and bug fixes. Breaking changes: * With this update, the `add_metric_suffixes` field of the Prometheus Exporter configuration in the `OpenTelemetryCollector` custom resource is removed. To manage metric name suffixes, use the `translation_strategy` field instead. Deprecations: * Google Cloud Exporter is deprecated: The Google Cloud Exporter, which sends telemetry data to Google Cloud Operations Suite, is deprecated and will be removed in a future major release. You can export data to Google Cloud Operations Suite by using the OTLP HTTP Exporter with the Google Client Authorization Extension instead. For more information, see https://redhat.atlassian.net/browse/TRACING-6139. Technology Preview features: * OBI (Open Telemetry eBPF) Receiver: This update adds the OBI (Open Telemetry eBPF) Receiver to the Red Hat build of OpenTelemetry as a Technology Preview feature. The OBI Receiver uses eBPF to automatically inspect application executables and the OS networking layer, and capture trace spans, Rate Errors Duration (RED) metrics. * Redaction Processor: This update adds the Redaction Processor to the Red Hat build of OpenTelemetry as a Technology Preview feature. The Redaction Processor removes sensitive data from telemetry data before it is exported. For more information, see https://redhat.atlassian.net/browse/TRACING-6502. * Headers Setter Extension: This update adds the Headers Setter Extension to the Red Hat build of OpenTelemetry as a Technology Preview feature. The Headers Setter Extension sets headers on outgoing HTTP requests made by exporters. For more information, see https://redhat.atlassian.net/browse/TRACING-6504. * Kubernetes Leader Elector Extension: This update adds the Kubernetes Leader Elector Extension to the Red Hat build of OpenTelemetry as a Technology Preview feature. The Kubernetes Leader Elector Extension enables OpenTelemetry components to run in HA mode across a Kubernetes cluster. The component that owns the lease becomes the leader and becomes the active instance. For more information, see https://redhat.atlassian.net/browse/TRACING-6478. Enhancements: * High availability for the Operator webhooks: This update introduces high availability support for the Red Hat build of OpenTelemetry Operator webhooks. The webhooks run in a separate deployment from the main Operator deployment. For more information, see https://redhat.atlassian.net/browse/TRACING-6157. Bug fixes: * Instrumentation CR status fields are updated automatically: Before this update, when creating or updating an Instrumentation custom resource (CR), the .status.observedGeneration and .status.conditions fields were not updated because the Red Hat build of OpenTelemetry Operator lacked a reconciliation controller for Instrumentation CRs. In this release, the Operator continuously reconciles Instrumentation CRs and populates these status fields upon creation or update without requiring an Operator restart. For more information, see https://issues.redhat.com/browse/TRACING-6412. * Automatic RBAC of the Operator includes PersistentVolume and PersistentVolumeClaim resources: Before this update, the automatic Role-Based Access Control (RBAC) feature of the Red Hat build of OpenTelemetry Operator did not include the required permissions for PersistentVolume and PersistentVolumeClaim resources. As a consequence, the Kubernetes Cluster Receiver failed with RBAC errors. With this update, the Operator automatically grants the required permissions for these resources. As a result, the Kubernetes Cluster Receiver works correctly with the automatic RBAC feature. For more information, see https://redhat.atlassian.net/browse/TRACING-6381.

CWE-409Improper Handling of Highly Compressed Data (Data Amplification) (opens in a new tab)
Base weakness
The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.2 (opens in a new tab)
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-409, CWE-190

Technical details

References

Community reviews

Related threats