CVE-2025-12970: FluentBit Fluent Bit · Stack-based Buffer Overflow
Affects FluentBit Fluent BitSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FluentBit Fluent Bit | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their Fluent Bit deployments to identify affected versions and usage of the in_docker input plugin. Since no official patches are listed yet, temporary mitigations include restricting the ability to create or rename containers with untrusted or excessively long names, enforcing container name length policies at the orchestration or container runtime level. Implement runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to reduce exploitation risk. Monitor container creation events and Fluent Bit logs for anomalous container names or crashes. Consider isolating Fluent Bit processes with minimal privileges and using container security tools to limit lateral movement. Stay alert for vendor patches or updates and apply them promptly once available. Incorporate this vulnerability into incident response plans and threat hunting activities targeting container environments.
Description
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 crash or arbitrary code execution.