Fluentd is widely used for logging in cloud-native environments; an RCE in its out_file plugin can broadly impact enterprise infrastructures.
CVE-2026-44024
Fluentd out_file tag path-traversal allows arbitrary file write and potential RCE.
Is CVE-2026-44024 being exploited?
Not confirmed. CVE-2026-44024 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.1% probability of exploitation in the next 30 days.
How severe is CVE-2026-44024?
CVE-2026-44024 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44024?
Yes. A fix has been recorded for CVE-2026-44024. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44024 affect?
CVE-2026-44024 affects Fluentd < 1.19.3, out_file plugin, Kubernetes/containers using Fluentd logging. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44024?
Upgrade to Fluentd >= 1.19.3; or disable out_file and sanitize tags until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can overwrite arbitrary files and achieve remote code execution via crafted ${tag} values in out_file paths.
Immediate action required
- affected< 1.19.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.