CVE-2026-44163
Received Received - Intake

Memory Exhaustion in fluent-plugin-opentelemetry

Vulnerability report for CVE-2026-44163, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
fluent-plugins-nursery fluent-plugin-opentelemetry to 0.5.3 (exc)
fluent-plugin-opentelemetry fluent-plugin-opentelemetry 0.5.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-409 The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-44163 is a Denial of Service (DoS) vulnerability in the fluent-plugin-opentelemetry plugin affecting the in_opentelemetry HTTP input component. The plugin does not enforce size limits on incoming requests, allowing it to read entire request bodies and decompress payloads into memory without restrictions. When exposed to untrusted networks, attackers can send excessively large HTTP requests or highly compressed payloads that expand significantly during decompression, causing rapid memory consumption and potential process termination due to Out-of-Memory errors.

Detection Guidance

Monitor Fluentd process memory usage and logs for Out-of-Memory errors. Check HTTP 413 errors in logs indicating payload size limits being exceeded. Use network monitoring tools to detect unusually large HTTP requests targeting OpenTelemetry ingestion ports (default 4318).

Commands: netstat -tulnp | grep 4318 to check listening ports, ps aux | grep fluentd to monitor Fluentd process, tail -f /var/log/fluent/fluentd.log for errors.

Impact Analysis

This vulnerability can disrupt log collection and forwarding on the affected node by causing the Fluentd process to crash due to memory exhaustion. If the OpenTelemetry ingestion endpoint is exposed to an untrusted network, attackers can exploit it to trigger a DoS condition, leading to service interruptions and potential loss of critical logging data.

Mitigation Strategies

Upgrade fluent-plugin-opentelemetry to version 0.5.3 or later. Restrict network access to OpenTelemetry ingestion ports using firewalls. Configure reverse proxies with strict size limits before forwarding traffic to Fluentd.

Set body_size_limit and decompression_size_limit parameters to enforce maximum payload sizes. Monitor logs for rejected requests to identify potential attack attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44163. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart