Most recent entries from all

EUVD-2026-369678

2026-10-08T12:15:56.301451+00:00

EUVD-2026-369678

fkie_cve-2026-44163

2026-10-08T12:15:56.301491+00:00

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.

GHSA-2jc5-xhx8-qj6h — fluent-plugin-opentelemetry Has Denial of Service (DoS) via Large Payloads and Decompression Bombs in `in_opentelemetry`

2026-10-08T12:15:56.301529+00:00

Affected: RubyGems: fluent-plugin-opentelemetry

The `fluent-plugin-opentelemetry` plugin (specifically the `in_opentelemetry` HTTP input) lacked strict size limits on incoming requests. It was discovered that the plugin read the entire request body and decompressed payloads into memory without enforcing maximum size thresholds.

If the OpenTelemetry ingestion endpoint is exposed to untrusted networks, an attacker can send an excessively large HTTP request or a maliciously crafted, highly compressed payload. When the plugin attempts to read or decompress this payload, it will expand to an excessive size and it will consume significant system resources.

### Impact This vulnerability allows for a **Denial of Service (DoS)** attack via memory exhaustion. The rapid memory consumption during decompression can easily lead to an Out-of-Memory kill of the Fluentd process by the operating system. This results in the disruption of all log collection and forwarding capabilities on the affected node.

### Patches v0.5.3

### Workarounds If an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:

1. Restrict Network Access * Ensure that the OpenTelemetry ingestion ports (default `4318`) are deployed within a closed, trusted network. Use firewall rules (e.g., iptables, AWS Security Groups) to block access from untrusted networks or instances. 2. Use a Reverse Proxy * If you must expose HTTP ingestion to external sources, place a robust reverse proxy (such as Nginx) in front of Fluentd…

jvndb-2026-000090

2026-10-08T12:15:56.301614+00:00

Fluentd provided by Fluentd Project contains multiple vulnerabilities listed below.

Path traversal in ${tag} Placeholder (CWE-22) - CVE-2026-44024
Missing authentication for critical function in Monitor Agent API (CWE-306) - CVE-2026-44025
Improper handling of highly compressed data in in_http and in_forward (CWE-409) - CVE-2026-44160
Server-side request forgery in out_http (CWE-918) - CVE-2026-44161
Improper handling of highly compressed data in in_s3 (CWE-409) - CVE-2026-44162
Improper handling of high…