Answer in brief
CVE-2026-44163 records a Medium severity (CVSS 5.3) vulnerability in fluent-plugin-opentelemetry: Denial of Service (DoS) via Large Payloads and Decompression Bombs in `in_opentelemetry`. The current sources do not mark it as known exploited. The current feed maps fluent-plugins-nursery/fluent-plugin-opentelemetry (generic), fluent-plugin-opentelemetry (rubygems), fluent-plugin-opentelemetry (rubygems). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps fluent-plugins-nursery/fluent-plugin-opentelemetry (generic), fluent-plugin-opentelemetry (rubygems), fluent-plugin-opentelemetry (rubygems). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| fluent-plugins-nursery/fluent-plugin-opentelemetrygeneric | < 0.5.3 | Not reported |
| fluent-plugin-opentelemetryrubygems | <=0.5.2 | 0.5.3 |
| fluent-plugin-opentelemetryrubygems | >=0 <0.5.3 | 0.5.3 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
fluent-plugin-opentelemetry is a Fluentd input and output plugin for forwarding OpenTelemetry Protocol data. Prior to 0.5.3, the in_opentelemetry HTTP input read the entire incoming request body and decompressed payloads into memory without enforcing maximum size thresholds. When an OpenTelemetry ingestion endpoint was exposed to an untrusted network, an attacker could send an excessively large request or a highly compressed payload that expanded in memory. The resulting memory exhaustion could cause the operating system to terminate the Fluentd process, disrupting all log collection and forwarding on the affected node. This issue is fixed in version 0.5.3.
Quoted source text, attributed separately from HOL analysis.