CVE-2025-12969: Fluent Bit in_forward input plugin does not properly enforce the security.users authentication
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 19 Nov 2026, 02:20 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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
Until a fix is available, users should review their Fluent Bit in_forward input plugin configurations to ensure that authentication mechanisms are properly enforced and consider restricting network access to the Fluent Bit instance to trusted sources only.
Description
A vulnerability in the Fluent Bit in_forward input plugin allows remote attackers to bypass the security.users authentication mechanism under certain configurations. This flaw permits unauthenticated data injection, potentially enabling attackers to forge log records, flood alerting systems, or alter routing decisions, thereby compromising log authenticity and integrity.
References
- nvd.nist.gov/vuln/detail/CVE-2025-12969 (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)