Affected: Bitnami: fluentd

Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Prior to 1.19.3, Fluentd allows dynamically constructing file paths using the ${tag} placeholder, and insufficient validation of ${tag} in file configurations such as the path parameter of the out_file plugin allows attackers sending untrusted tags containing path traversal characters to write or overwrite arbitrary files and potentially achieve remote code execution. This issue is fixed in version 1.19.3.

Affected: CleanStart: kube-logging-operator

Security vulnerability affects the kube-logging-operator package. This issue is resolved in later releases. See references for vulnerability details.

Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Prior to 1.19.3, Fluentd allows dynamically constructing file paths using the ${tag} placeholder, and insufficient validation of ${tag} in file configurations such as the path parameter of the out_file plugin allows attackers sending untrusted tags containing path traversal characters to write or overwrite arbitrary files and potentially achieve remote code execution. This issue is fixed in version 1.19.3.

Affected: RubyGems: fluentd

Fluentd allows dynamically constructing file paths using the `${tag}` placeholder. It was discovered that validation for this placeholder was insufficient.

If a Fluentd instance is configured to receive logs from untrusted sources and uses the `${tag}` placeholder in file configurations (such as the `path` parameter in the `out_file` plugin), an attacker can inject path traversal characters (e.g., `../`).

When combined with certain formatting options, this vulnerability allows an attacker to write arbitrary files or overwrite existing files on the system with attacker-controlled content, bypassing intended directory restrictions.

### Impact This vulnerability allows for **Arbitrary File Write**, which can be directly escalated to full **Remote Code Execution (RCE)**. An attacker could achieve RCE by overwriting critical system files, injecting executable plugins, or modifying configuration files. The impact is Critical as it can lead to full system compromise without any authentication, depending on the Fluentd configuration and the privileges of the Fluentd process.

### Patches v1.19.3

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

1. Restrict Network Access * Ensure that Fluentd input ports (such as `in_forward` on default port `24224`) are deployed within a closed, trusted network. Use firewall rules (e.g., iptables, AWS Security Groups) to block access from untrusted networks or instances.…

Fluentd provided by Fluentd Project contains multiple vulnerabilities listed below. <a href='https://cwe.mitre.org/data/definitions/22.html' target='_blank'></a><a href='https://www.cve.org/CVERecord?id=CVE-2026-44024' target='_blank'></a><a href='https://cwe.mitre.org/data/definitions/306.html' target='_blank'></a><a href='http://www.cve.org/CVERecord?id=CVE-2026-44025' target='_blank'></a> <a href='https://cwe.mitre.org/data/definitions/409.html' target='_blank'></a><a href='http://www.cve.org/CVERecord?id=CVE-2026-44160' target='_blank'></a> <a href='https://cwe.mitre.org/data/definitions/918.html' target='_blank'></a><a href='http://www.cve.org/CVERecord?id=CVE-2026-44161' target='_blank'></a> <a href='https://cwe.mitre.org/data/definitions/409.html' target='_blank'></a><a href='http://www.cve.org/CVERecord?id=CVE-2026-44162' target='_blank'></a> <a href='https://cwe.mitre.org/data/definitions/409.html' target='_blank'></a><a href='http://www.cve.org/CVERecord?id=CVE-2026-44163' target='_blank'></a><ul><li>Path traversal in ${tag} Placeholder (CWE-22) - CVE-2026-44024</li><li>Missing authentication for critical function in Monitor Agent API (CWE-306) - CVE-2026-44025</li><li>Improper handling of highly compressed data in in_http and in_forward (CWE-409) - CVE-2026-44160</li><li>Server-side request forgery in out_http (CWE-918) - CVE-2026-44161</li><li>Improper handling of highly compressed data in in_s3 (CWE-409) - CVE-2026-44162</li><li>Improper handling of high…

Affected: openEuler:24.03-LTS-SP3: rubygem-fluentd

Fluentd is an open source data collector designed to scale and simplify log management. It can collect, process and ship many kinds of data in near real-time. Security Fix(es):

Fluentd allows dynamically constructing file paths using the `${tag}` placeholder. It was discovered that validation for this placeholder was insufficient.

If a Fluentd instance is configured to receive logs from untrusted sources and uses the `${tag}` placeholder in file configurations (such as the `path` parameter in the `out_file` plugin), an attacker can inject path traversal characters (e.g., `../`).

When combined with certain formatting options, this vulnerability allows an attacker to write arbitrary files or overwrite existing files on the system with attacker-controlled content, bypassing intended directory restrictions.

### Impact This vulnerability allows for **Arbitrary File Write**, which can be directly escalated to full **Remote Code Execution (RCE)**. An attacker could achieve RCE by overwriting critical system files, injecting executable plugins, or modifying configuration files. The impact is Critical as it can lead to full system compromise without any authentication, depending on the Fluentd configuration and the privileges of the Fluentd process.

### Patches v1.19.3

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

1. Restrict Network Access * Ensure that Fluentd input ports (such as `in_forward` on…

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Fluentd ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen oder einen Denial of Service zu verursachen.