CVE-2026-44024: Fluentd Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-44hj-4m45-frj3
CVSS 9.8
CWE-94 CWE-22
Published
Advisory Summary

CVE-2026-44024 is a CRITICAL (CVSS 9.8) remote code execution vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Fluentd libraries in the RubyGems ecosystem. The issue involves fluentd is vulnerable to remote code execution (rce) via arbitrary file write in `${tag}` placeholder. Remediation is available by upgrading affected packages to version 1.19.3.

CVE-2026-44024 at a Glance

CVE Identifier CVE-2026-44024
GHSA Identifier GHSA-44hj-4m45-frj3
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Fluentd
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-44024

To remediate this vulnerability, upgrade all affected Fluentd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

fluentd fixed: 1.19.3
Upgrade fluentd to 1.19.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for fluentd

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44024, inspect your project dependencies for Fluentd:

inspect dependencies for fluentd

Analyze the terminal output to locate any version of Fluentd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.19.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Fluentd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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. 2. Run Fluentd as a non-root user * Dropping privileges prevents Fluentd from writing to sensitive system directories (e.g., `/etc/`), significantly mitigating the risk of system-wide RCE. 3. Revise configurations * Do not use the `${tag}` placeholder in the `path` parameter of output plugins (like `out_file`) if the tag originates from an untrusted source. 4. Filter incoming tags * Strictly validate and filter incoming tags at the input layer (e.g., using `fluent-plugin-rewrite-tag-filter`) to drop any tags containing `.` or `/` characters.

CVE-2026-44024 Affected Fluentd Versions

1 component(s)
Fixed Versions:
1.19.3
Product / Package Ecosystem Affected Versions Fixed Version
fluentd
RubyGems
< 1.19.3
1.19.3

References

Frequently Asked Questions

What is CVE-2026-44024?
CVE-2026-44024 is a security vulnerability in Fluentd involving Fluentd is Vulnerable to Remote Code Execution (RCE) via Arbitrary File Write in `${tag}` Placeholder under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Fluentd versions are affected?
Affected versions include releases prior to 1.19.3 across affected packages: fluentd.
What version fixes CVE-2026-44024?
Upgrading to 1.19.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is fluentd affected?
Yes, fluentd is affected in releases prior to 1.19.3. Upgrade your dependency to 1.19.3 or later.
What is the CVSS score of CVE-2026-44024?
CVE-2026-44024 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-44024?
CVE-2026-44024 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check RubyGems dependencies for CVE-2026-44024?
Run the dependency tree command: 'inspect dependencies for fluentd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-44hj-4m45-frj3",
  "modified" : "2026-06-26T16:32:05Z",
  "published" : "2026-06-26T16:32:05Z",
  "aliases" : [ "CVE-2026-44024" ],
  "summary" : "Fluentd is Vulnerable to Remote Code Execution (RCE) via Arbitrary File Write in `${tag}` Placeholder",
  "details" : "Fluentd allows dynamically constructing file paths using the `${tag}` placeholder.\nIt was discovered that validation for this placeholder was insufficient.\n\nIf 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., `../`).\n\nWhen 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.\n\n### Impact\nThis vulnerability allows for **Arbitrary File Write**, which can be directly escalated to full **Remote Code Execution (RCE)**.\nAn attacker could achieve RCE by overwriting critical system files, injecting executable plugins, or modifying configuration files.\nThe 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.\n\n### Patches\nv1.19.3\n\n### Workarounds\nIf an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:\n\n1. Restrict Network Access\n   * 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.\n2. Run Fluentd as a non-root user\n   * Dropping privileges prevents Fluentd from writing to sensitive system directories (e.g., `/etc/`), significantly mitigating the risk of system-wide RCE.\n3. Revise configurations\n   * Do not use the `${tag}` placeholder in the `path` parameter of output plugins (like `out_file`) if the tag originates from an untrusted source.\n4. Filter incoming tags\n   * Strictly validate and filter incoming tags at the input layer (e.g., using `fluent-plugin-rewrite-tag-filter`) to drop any tags containing `.` or `/` characters.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "fluentd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.19.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.19.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fluent/fluentd/security/advisories/GHSA-44hj-4m45-frj3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fluent/fluentd"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fluent/fluentd/releases/tag/v1.19.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T16:32:05Z",
    "nvd_published_at" : null
  }
}