Skip to main content
CVE-2025-12978VulnerabilityPublished

Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins contain a flaw in the tag_key validation logic that

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-12978· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 17 Nov 2026, 01:38 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

AI-suggested

Until a fix is available, restrict access to the affected input endpoints to trusted users only and monitor for suspicious tag manipulation activities.

Description

A flaw in Fluent Bit's in_http, in_splunk, and in_elasticsearch input plugins causes improper validation of the tag_key, allowing tag prefixes to be misinterpreted as full matches. This vulnerability enables remote attackers with authenticated or exposed access to manipulate log tags, redirect records, and inject forged data, potentially causing alert flooding and routing manipulation.

References

Community reviews

Loading reviews…