CVE-2026-44160

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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, Fluentd's in_http and in_forward plugins support gzip-compressed data but enforce limits only on compressed payloads through settings such as body_size_limit and chunk_size_limit, allowing crafted compressed payloads to decompress in memory to an excessive size and cause denial of service through memory exhaustion. This issue is fixed in version 1.19.3.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

Published

June 26, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
githubMentions a patch (unverified)

Denial of Service (DoS) via Gzip Decompression Bomb in `in_http` and `in_forward` · Advisory · fluent/fluentd · GitHub

https://github.com/fluent/fluentd/security/advisories/GHSA-j9cw-hwqf-85w7
github_release Patch Available

Fluentd v1.19.3

Patch available: fluent/fluentd v1.19.3

https://github.com/fluent/fluentd/releases/tag/v1.19.3
github_pr Patch Available

Backport(v1.19) buffer, in_http: enforce size limits on decompressed payloads

Patch available: fluent/fluentd v1.19.3 (PR #5393 merged 2026-06-25)

https://github.com/fluent/fluentd/pull/5393
github_commit Patch Available

commit f5f2b7cddf8a (fluent/fluentd)

Patch available: fluent/fluentd v1.19.3 (contains commit f5f2b7cddf8a)

https://github.com/fluent/fluentd/commit/f5f2b7cddf8aab3932e6dec9fa367a5f3eb27e10

Vendor Advisories for CVE-2026-44160(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
fluentd0.10.0 ... 1.9.3 (242 versions)
  • every version up to 1.19.3: fixed in 1.19.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 118 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-23 07:51 UTCEG score recompute
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 07:13 UTCEG score recompute
  18. 2026-09-17 19:31 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 01:11 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:35 UTCEG score recompute
  24. 2026-09-12 15:01 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-10 09:34 UTCEPSS rescore
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-08-30 19:21 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 23:06 UTCEG score recompute
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 00:54 UTCEG score recompute
  18. 2026-08-24 12:54 UTCEG score recompute
  19. 2026-08-23 09:51 UTCEG score recompute
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-22 09:32 UTCEG score recompute
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 07:13 UTCEG score recompute
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 06:51 UTCEG score recompute
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-18 23:55 UTCEG score recompute
  28. 2026-08-18 13:48 UTCEPSS rescore
  29. 2026-08-17 13:47 UTCEPSS rescore
  30. 2026-08-16 20:18 UTCEG score recompute
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 08:17 UTCEG score recompute
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 08:16 UTCEG score recompute
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 06:25 UTCEG score recompute
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-12 17:56 UTCEG score recompute
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 17:28 UTCEG score recompute
  41. 2026-08-11 13:43 UTCEPSS rescore
  42. 2026-08-11 05:13 UTCEG score recompute
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-09 16:53 UTCEG score recompute
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-08 16:53 UTCEG score recompute
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-07 16:52 UTCEG score recompute
  49. 2026-08-06 16:51 UTCEG score recompute
  50. 2026-08-06 13:46 UTCEPSS rescore
  51. 2026-08-06 04:51 UTCEG score recompute
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-05 02:58 UTCEG score recompute
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 14:58 UTCEG score recompute
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-03 14:14 UTCEG score recompute
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-02 14:10 UTCEG score recompute
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 14:09 UTCEG score recompute
  62. 2026-08-01 04:16 UTCEPSS rescore
  63. 2026-07-31 01:26 UTCEG score recompute
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 13:23 UTCEG score recompute
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-28 20:26 UTCEG score recompute
  68. 2026-07-28 15:36 UTCEPSS rescore
  69. 2026-07-27 17:06 UTCEG score recompute
  70. 2026-07-27 14:13 UTCEPSS rescore
  71. 2026-07-27 02:35 UTCEG score recompute
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:34 UTCEG score recompute
  75. 2026-07-25 14:18 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-44160?
CVE-2026-44160 is a high vulnerability published on June 26, 2026. 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, Fluentd's inhttp and inforward plugins support gzip-compressed data but enforce limits only on compressed payloads through settings such as bodysizelimit and…
When was CVE-2026-44160 disclosed?
CVE-2026-44160 was first published on June 26, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44160 actively exploited?
CVE-2026-44160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44160?
CVE-2026-44160 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44160?
A fix for CVE-2026-44160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44160 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44160

Explore →

Is Your Infrastructure Affected by CVE-2026-44160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs