Is fluentd 1.17 vulnerable?
RubyGems · 2 releases from 1.17.0 to 1.17.1 · latest fluentd is 1.20.1 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. fluentd 1.17.1, the last 1.17 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.
bundle update --conservative fluentd # Gemfile: '>= 1.19.3'Is your project on an affected fluentd?
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.17.1
Fluentd is Vulnerable to Server-Side Request Forgery (SSRF) via Placeholder Expansion in `out_http`
- Affected
- <1.19.3
- Fixed in
- 1.19.3
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
Fluentd is Vulnerable to Exposure of Sensitive Information via Monitor Agent API
- Affected
- <1.19.3
- Fixed in
- 1.19.3
Fluentd is Vulnerable to Remote Code Execution (RCE) via Arbitrary File Write in `${tag}` Placeholder
- Affected
- <1.19.3
- Fixed in
- 1.19.3
Every fluentd 1.17.x release
Affected: 1.17.0 to 1.17.1. Latest fluentd: 1.20.1.
| Version | Known advisories |
|---|---|
| fluentd 1.17.1 | CVE-2026-44161, CVE-2026-44160, CVE-2026-44025, CVE-2026-44024 |
| fluentd 1.17.0 | CVE-2026-44161, CVE-2026-44160, CVE-2026-44025, CVE-2026-44024 |
Which of your client projects are still on fluentd 1.17?
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.