Skip to content

Vendor

FluentBit vulnerabilities

5 published CVES affecting FluentBit, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
5
Critical
1
High
1
Medium
3
Low
0
Unscored
0
CISA KEV
0
Atom feed of FluentBit alerts

Products

Latest FluentBit CVEs

Newest publication first

  1. CVE-2025-12978 CVE-2025-12978

    Published
    MediumCVSS 5.4 EPSS 0.41%

    Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins contain a flaw in the tag_key validation logic that fails to enforce exact key-length matching. This allows crafted inputs where a tag prefix is incorrectly treated as a full match. A remote attacker with authentic...

  2. CVE-2025-12969 CVE-2025-12969

    Published
    MediumCVSS 6.5 EPSS 0.63%

    Fluent Bit in_forward input plugin does not properly enforce the security.users authentication mechanism under certain configuration conditions. This allows remote attackers with network access to the Fluent Bit instance exposing the forward input to send unauthenticated data. By...

  3. CVE-2025-12972 CVE-2025-12972

    Published
    MediumCVSS 5.3 EPSS 0.93%

    Fluent Bit out_file plugin does not properly sanitize tag values when deriving output file names. When the File option is omitted, the plugin uses untrusted tag input to construct file paths. This allows attackers with network access to craft tags containing path traversal sequen...

  4. CVE-2025-12977 CVE-2025-12977

    Published
    CriticalCVSS 9.1 EPSS 0.76%

    Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with network access or the ability to write records into Splunk or Elasticsearch can supply tag_key values containing special characters such as newlines or ../ that are...

  5. CVE-2025-12970 CVE-2025-12970

    Published
    HighCVSS 8.8 EPSS 1.1%

    The extract_name function in Fluent Bit in_docker input plugin copies container names into a fixed size stack buffer without validating length. An attacker who can create containers or control container names, can supply a long name that overflows the buffer, leading to process c...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.