Most recent entries from all

BIT-fluentd-2026-44161 — Fluentd: Server-Side Request Forgery (SSRF) via Placeholder Expansion in `out_http`

2026-10-04T00:30:28.376964+00:00

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, the Fluentd out_http output plugin allows placeholders such as ${tag} in the endpoint configuration parameter, and if a placeholder value is derived from untrusted input an attacker can control the destination hostname of outbound HTTP requests and force requests to arbitrary internal services. This issue is fixed in version 1.19.3.

certfr-2026-avi-0958 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…

2026-10-04T00:30:28.377018+00:00

certfr-2026-avi-0958

CLEANSTART-2026-RY78730 — Security fix for CVE-2026-44161 applied in: kube-logging-operator 6.7.0-r2

2026-10-04T00:30:28.377038+00:00

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.

EUVD-2026-335365

2026-10-04T00:30:28.377059+00:00

EUVD-2026-335365

fkie_cve-2026-44161

2026-10-04T00:30:28.377070+00:00

GHSA-72f5-rr8c-r6gr — Fluentd is Vulnerable to Server-Side Request Forgery (SSRF) via Placeholder Expansion in `out_http`

2026-10-04T00:30:28.377091+00:00

Affected: RubyGems: fluentd

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.

### 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`).

### Patches v1.19.3

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

1. Avoid Dynamic Hostnames * Do not use the placeholder in the endpoint parameter as hostname.

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's metadata service and other internal microservices that Fluentd does not explicitly need to access.

3. Restrict allowed hosts * Inject filter to accept allowed hosts in placeholders explicitly if possible.

jvndb-2026-000090

2026-10-04T00:30:28.377122+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…

WID-SEC-W-2026-2096 — Fluentd: Mehrere Schwachstellen

2026-10-04T00:30:28.377156+00:00

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