Vulnerability Database · OSS-Fuzz · Package report

fluent-bit: vulnerability history, versions and safety

fluent-bit is a package in the OSS-Fuzz ecosystem. Vulert records 81 vulnerabilities for it across 120 releases, from Jun 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
81 vulnerabilities recorded H37 M36 U8
i
13 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 06 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on fluent-bit i

Updated on 23 Oct 2026

Careful: 13 of the 81 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 81 vulnerabilities on record across 6 years, 2 in the last year.

What to do: Plan around the 13 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 81 over 6 years · 2 in the last year i
  • Latest disclosure 06 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 13 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for fluent-bit, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
20220215 M3 No Details →
1.8.9-dev-6b56f51 M3 No Details →
v5.1.1 M1 Yes Details →
v5.1.0 M1 Yes Details →
v5.0.9 M1 Yes Details →
v5.0.8 M1 Yes Details →
v5.0.7 M1 Yes Details →
v5.0.6 M1 Yes Details →
v5.0.5 M1 Yes Details →
v5.0.4 M1 Yes Details →
v5.0.3 M1 Yes Details →
v5.0.2 M1 Yes Details →
v5.0.1 M1 Yes Details →
v5.0.0 M1 Yes Details →
v5.0.0-dev-20260228 M1 Yes Details →
v4.2.2 H1 M1 Yes Details →
v4.2.1 H1 M1 Yes Details →
v4.0.8 H2 No Details →
v4.0.7 H2 No Details →
v4.0.6 H2 No Details →
v4.0.5 H2 No Details →
v4.0.4 H2 No Details →
v4.0.3 H2 No Details →
v4.0.2 H2 No Details →
v4.0.1 H2 M1 U1 No Details →
v4.0.0 H2 M1 U1 No Details →
v3.2.10 H2 M1 U1 No Details →
v3.2.9 H2 M1 U1 No Details →
v3.2.8 H2 M1 U1 No Details →
v3.2.7 H2 M1 U1 No Details →
v3.2.6 H2 M1 U1 No Details →
v3.2.5 H2 M1 U1 No Details →
v3.2.4 H2 M1 U1 No Details →
v3.2.3 H2 M1 U1 No Details →
v3.2.2 H2 M1 U1 No Details →
v3.2.1 H2 M1 U1 No Details →
v3.2.0 H2 M1 U1 No Details →
v3.1.10 H2 M1 U1 No Details →
v3.1.9 H2 M1 U1 No Details →
v3.1.8 H2 M1 U1 No Details →
v3.1.7 H2 M1 U1 No Details →
v3.1.6 H3 M1 U2 No Details →
v3.1.5 H3 M1 U2 No Details →
v3.1.4 H3 M1 U2 No Details →
v3.1.3 H3 M1 U2 No Details →
v3.1.2 H3 M1 U2 No Details →
v3.1.1 H3 M1 U2 No Details →
v3.1.0 H3 M1 U2 No Details →
v3.0.7 H3 M1 U2 No Details →
v3.0.6 H3 M1 U2 No Details →
v3.0.5 H3 M1 U2 No Details →
v3.0.4 H3 M1 U2 No Details →
v3.0.3 H3 M1 U2 No Details →
v3.0.2 H3 M1 U2 No Details →
v3.0.1 H3 M1 U2 No Details →
v3.0.0 H3 M1 U2 No Details →
v2.2.3 H3 M1 U2 No Details →
v2.2.2 H3 M1 U2 No Details →
v2.2.1 H3 M1 U2 No Details →
v2.2.0 H3 M1 U2 No Details →
v2.1.10 H3 M1 U2 No Details →
v2.1.9 H3 M1 U2 No Details →
v2.1.8 H3 M1 U2 No Details →
v2.1.7 H3 M1 U2 No Details →
v2.1.6 H3 M1 U2 No Details →
v2.1.5 H3 M1 U2 No Details →
v2.1.5-windows-artifact-fix H3 M1 U2 No Details →
v2.1.4 H2 No Details →
v2.1.3 H2 No Details →
v2.1.2 H2 No Details →
v2.1.1 H2 No Details →
v2.1.0 H2 No Details →
v2.1.0-rc2 H2 No Details →
v2.1.0-rc1 H2 No Details →
v2.0.14 H2 No Details →
v2.0.13 H2 No Details →
v2.0.12 H2 No Details →
v2.0.11 H2 No Details →
v2.0.10 H2 No Details →
v2.0.9 H2 No Details →
tiger-2.0.9-dev-20230104 H2 M5 No Details →
v2.0.8 H2 M5 No Details →
v2.0.7 H2 M5 No Details →
vv.2.0.7 H2 M5 No Details →
v2.0.6 H3 M6 No Details →
v2.0.5 H3 M6 No Details →
v2.0.4 H3 M6 No Details →
v2.0.3 H3 M6 No Details →
v2.0.2 H3 M6 No Details →
v2.0.1 H3 M6 No Details →
v2.0.0pre H3 M6 No Details →
v2.0.0 H3 M6 No Details →
v2.0.0-rc3 H3 M6 No Details →
v2.0.0-rc2 H3 M6 No Details →
v2.0.0-rc1 H3 M6 No Details →
v1.9.10 H5 M6 U1 Yes Details →
v1.9.9 H5 M6 U1 Yes Details →
v1.9.8 H5 M6 U2 Yes Details →
v1.9.7 H7 M6 U2 Yes Details →
v1.9.6 H7 M6 U2 Yes Details →
v1.9.5 H6 M6 U2 Yes Details →
v1.9.4 H6 M6 U2 Yes Details →
v1.9.3 H6 M6 U2 Yes Details →
v1.9.2 H6 M6 U2 Yes Details →
v1.9.1 H6 M6 U2 Yes Details →
v1.9.0 H5 M7 U1 Yes Details →
v1.9.0-rc4 H5 M7 U1 Yes Details →
v1.9.0-rc3 H5 M7 U1 Yes Details →
v1.9.0-rc2 H4 M6 U1 Yes Details →
v1.9.0-rc1 H4 M6 U1 Yes Details →
v1.9.0-ci-test-1 H5 M7 U1 Yes Details →
tiger-1.8.15-20230329 M2 No Details →
tiger-1.8.15-20230223 M3 No Details →
tiger-1.8.15-20221220 M3 No Details →
tiger-1.8.15-20221123 M3 No Details →
v1.8.15 M3 No Details →
v1.8.14 M3 No Details →
v1.8.13 M3 No Details →
v1.8.12 M3 No Details →
v1.8.11 M3 No Details →

Newest 120 of 172 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 27
  • 2021 14
  • 2022 33
  • 2023 4
  • 2024 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 81 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for fluent-bit

The 5 most severe of 81 vulnerabilities recorded for this package

Search all 81 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in onig_node_str_cat in fluent-bit N/A medium 5ddb06fe4273bdec0171bc30877959c7bef666c2 29 Sep 2022
Heap Buffer Overflow Vulnerability in Fluent Bit N/A high d6e65fb019a28ec2b16221e2753d4e3284e06ad0 03 Jan 2026
Heap-double-free vulnerability in fluent-bit N/A high cee783e53b96e445983a667ba51da087df14e472 19 Mar 2022
Segv on unknown address in flb_config_map_properties_check in fluent-bit N/A unrated cee783e53b96e445983a667ba51da087df14e472 19 Mar 2022
Heap-double-free vulnerability in fluent-bit N/A high af7ef37d6f0c61a79a8bd66f603273245198e069 19 Mar 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About fluent-bit

Is fluent-bit safe to use?

Vulert records 81 vulnerabilities for fluent-bit in OSS-Fuzz: 0 critical, 37 high, 36 medium and 0 low, plus 8 not yet rated. 13 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does fluent-bit have?

81 vulnerabilities are recorded for fluent-bit in the OSS-Fuzz ecosystem: 0 critical, 37 high, 36 medium and 0 low, plus 8 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new fluent-bit vulnerabilities disclosed?

2 vulnerabilities were recorded for fluent-bit in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of fluent-bit are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor fluent-bit for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the fluent-bit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.