CVE-2025-12977: Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical.
Data as of 19 Nov 2026, 02:18 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
AI-suggested
Users should monitor vendor advisories for updates. In the meantime, restrict network access to Fluent Bit input plugins to trusted sources only and validate or sanitize tag_key inputs upstream if possible to mitigate risk.
Description
Fluent Bit's in_http, in_splunk, and in_elasticsearch input plugins do not properly sanitize tag_key inputs. This allows an attacker with network access or the ability to write records into Splunk or Elasticsearch to supply tag_key values containing special characters such as newlines or path traversal sequences. These malformed tags can lead to newline injection, path traversal, forged record injection, or log misrouting, affecting data integrity and log routing.
References
- nvd.nist.gov/vuln/detail/CVE-2025-12977 (opens in a new tab)
- fluentbit.io/announcements/v4.1.0 (opens in a new tab)
- fluentbit.io/blog/2025/10/28/security-vulnerabilities-addressed-in-fluent-bit-v4.1-and-backported-to-v4.0 (opens in a new tab)
- oligo.security/blog/critical-vulnerabilities-in-fluent-bit-expose-cloud-environments-to-remote-takeover (opens in a new tab)