CVE-2025-12970: extract_name function
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 19 Nov 2026, 02:18 UTC
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
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, restrict the ability to create or name containers to trusted users only to reduce risk.
Description
CVE-2025-12970 is a high-severity buffer overflow vulnerability in the extract_name function of the Fluent Bit in_docker input plugin. The function copies container names into a fixed-size stack buffer without validating the length, allowing an attacker who can create or control container names to supply an overly long name. This can cause a process crash or enable arbitrary code execution.
References
- nvd.nist.gov/vuln/detail/CVE-2025-12970 (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)