Local code execution via unchecked container-name copy
Published Nov 24, 2025 · Updated Jan 7, 2026
Stack-based buffer overflow in Fluent Bit before 4.0.12 allows local users to crash the agent or execute code via a long container name. The in_docker plugin's extract_name function copies the Docker API name into a fixed-size stack buffer without first validating its length. Exploitation requires control of container names and use of the Docker input; successful code execution compromises the host-side Fluent Bit process.
Summary
What happened
Stack-based buffer overflow in Fluent Bit before 4.0.12 allows local users to crash the agent or execute code via a long container name. The in_docker plugin's extract_name function copies the Docker API name into a fixed-size stack buffer without first validating its length. Exploitation requires control of container names and use of the Docker input; successful code execution compromises the host-side Fluent Bit process.
The record
- CVE
- CVE-2025-12970
- Published
- Nov 24, 2025
- Updated
- Jan 7, 2026
- Vendor
- Fluent Bit
- Product
- Fluent Bit
- Classifications
- CWE-121, CWE-120, T1499, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 24, 2025CVE publishedPublication date reported by the CVE source.
- Jan 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.0.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo