Is fluentd 1.18 vulnerable?

RubyGems · 1 release from 1.18.0 to 1.18.0 · latest fluentd is 1.20.1 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. fluentd 1.18.0, the last 1.18 release, is affected by 4 known security advisories (1 critical, 3 high), including CVE-2026-44024, CVE-2026-44161, CVE-2026-44160. Upgrade to 1.19.3 or later to fix all of them.

Upgrade with:bundle update --conservative fluentd # Gemfile: '>= 1.19.3'

Is your project on an affected fluentd?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting fluentd 1.18.0

  • HighCVE-2026-44161GHSA-72f5-rr8c-r6gr26 Jun 2026

    Fluentd is Vulnerable to Server-Side Request Forgery (SSRF) via Placeholder Expansion in `out_http`

    Affected
    <1.19.3
    Fixed in
    1.19.3
  • HighCVE-2026-44160GHSA-j9cw-hwqf-85w726 Jun 2026

    Fluentd is Vulnerable to Denial of Service (DoS) via Gzip Decompression Bomb in `in_http` and `in_forward`

    Affected
    <1.19.3
    Fixed in
    1.19.3
  • HighCVE-2026-44025GHSA-pr7j-96cj-549h26 Jun 2026

    Fluentd is Vulnerable to Exposure of Sensitive Information via Monitor Agent API

    Affected
    <1.19.3
    Fixed in
    1.19.3
  • CriticalCVE-2026-44024GHSA-44hj-4m45-frj326 Jun 2026

    Fluentd is Vulnerable to Remote Code Execution (RCE) via Arbitrary File Write in `${tag}` Placeholder

    Affected
    <1.19.3
    Fixed in
    1.19.3

Which of your client projects are still on fluentd 1.18?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact fluentd version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other fluentd versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.