https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 16:00:52 +0000 https://cve.radiocsirt.org/vuln/cve-2026-44024 <p><strong>Affected:</strong> fluentd</p> <p>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.</p> <p><strong>Affected:</strong> fluentd</p> <p>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.</p> https://cve.radiocsirt.org/vuln/cve-2026-44024 https://cve.radiocsirt.org/vuln/ghsa-72f5-rr8c-r6gr <p><strong>Affected:</strong> RubyGems: fluentd</p> <p>The `out_http` output plugin allows the use of placeholders (such as `${tag}`) in the `endpoint` configuration parameter. It was discovered that if the placeholder value is derived from untrusted user input, an attacker can maliciously control the destination hostname of the outbound HTTP requests made by Fluentd.</p> <p>### Impact This vulnerability allows for a **Server-Side Request Forgery (SSRF)** attack. An unauthenticated attacker can force the Fluentd node to send HTTP requests to arbitrary internal services. This can lead to unauthorized access to internal APIs, data exfiltration, or the compromise of cloud metadata endpoints (e.g., AWS IMDS `169.254.169.254`).</p> <p>### Patches v1.19.3</p> <p>### Workarounds If an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:</p> <p>1. Avoid Dynamic Hostnames * Do not use the placeholder in the endpoint parameter as hostname.</p> <p>2. Restrict Network Access * Use firewall rules (e.g., iptables, AWS Security Groups) to block the Fluentd node from accessing sensitive internal IP addresses, specifically the cloud provider&#39;s metadata service and other internal microservices that Fluentd does not explicitly need to access.</p> <p>3. Restrict allowed hosts * Inject filter to accept allowed hosts in placeholders explicitly if possible.</p> <p><strong>Affected:</strong> RubyGems: fluentd</p> <p>The `out_http` output plugin allows the use of placeholders (such as `${tag}`) in the `endpoint` configuration parameter. It was discovered that if the placeholder value is derived from untrusted user input, an attacker can maliciously control the destination hostname of the outbound HTTP requests made by Fluentd.</p> <p>### Impact This vulnerability allows for a **Server-Side Request Forgery (SSRF)** attack. An unauthenticated attacker can force the Fluentd node to send HTTP requests to arbitrary internal services. This can lead to unauthorized access to internal APIs, data exfiltration, or the compromise of cloud metadata endpoints (e.g., AWS IMDS `169.254.169.254`).</p> <p>### Patches v1.19.3</p> <p>### Workarounds If an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:</p> <p>1. Avoid Dynamic Hostnames * Do not use the placeholder in the endpoint parameter as hostname.</p> <p>2. Restrict Network Access * Use firewall rules (e.g., iptables, AWS Security Groups) to block the Fluentd node from accessing sensitive internal IP addresses, specifically the cloud provider&#39;s metadata service and other internal microservices that Fluentd does not explicitly need to access.</p> <p>3. Restrict allowed hosts * Inject filter to accept allowed hosts in placeholders explicitly if possible.</p> https://cve.radiocsirt.org/vuln/ghsa-72f5-rr8c-r6gr