CVE-2025-12972: Fluent Bit out_file plugin does not properly sanitize tag values when deriving output file names
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 02:19 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
Users should avoid omitting the File option in the out_file plugin configuration to prevent the use of untrusted tag input for file path construction. Monitor vendor advisories for updates and apply official patches once released.
Description
CVE-2025-12972 is a vulnerability in the Fluent Bit out_file plugin where tag values are not properly sanitized when used to derive output file names. If the File option is omitted, untrusted tag input can be used to construct file paths, enabling attackers with network access to perform path traversal and write files outside the intended directory.
References
- nvd.nist.gov/vuln/detail/CVE-2025-12972 (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)