CVE-2025-12970

Memory Safety in Treasuredata Fluent Bit 4.1.0

Memory Safety

Published

24 November 2025

Modified

28 November 2025

CVSS Score v3.1 8.8

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Score 0.0088 56th percentile

Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2025-12970 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Treasuredata Fluent Bit. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-12970 is a buffer overflow vulnerability (CWE-120) in the extract_name function of the in_docker input plugin in Fluent Bit. The function copies container names into a fixed-size stack buffer without validating the input length, which can lead to a stack-based buffer overflow. This issue affects Fluent Bit deployments that utilize the in_docker plugin for monitoring Docker containers, with a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

An attacker with low privileges (PR:L) who can create containers or control container names can exploit this vulnerability over the network with low complexity and no user interaction required. By supplying an excessively long container name, the attacker triggers the buffer overflow, potentially causing a denial-of-service via process crash or achieving arbitrary code execution with high impact on confidentiality, integrity, and availability.

Advisories from Fluent Bit and security researchers indicate that the vulnerability has been addressed in Fluent Bit version 4.1, with backports available for version 4.0. Security practitioners should update to these patched versions and review configurations using the in_docker plugin in cloud or containerized environments.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2025-198809

Vulnerability Data

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.

CWE(s): CWE-120

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.

attack.mitre.org →

T1190 Exploit Public-Facing Application Initial Access

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.

attack.mitre.org →

T1203 Exploitation for Client Execution Execution

Adversaries may exploit software vulnerabilities in client applications to execute code.

attack.mitre.org →

T1210 Exploitation of Remote Services Lateral Movement

Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.

attack.mitre.org →

T1212 Exploitation for Credential Access Credential Access

Adversaries may exploit software vulnerabilities in an attempt to collect credentials.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-26455Same product: Treasuredata Fluent Bit

CVE-2025-12977Same product: Treasuredata Fluent Bit

CVE-2024-4323Same product: Treasuredata Fluent Bit

CVE-2025-12972Same product: Treasuredata Fluent Bit

CVE-2025-12969Same product: Treasuredata Fluent Bit

CVE-2024-23722Same product: Treasuredata Fluent Bit

CVE-2025-29478Same product: Treasuredata Fluent Bit

CVE-2024-50608Same product: Treasuredata Fluent Bit

CVE-2025-12978Same product: Treasuredata Fluent Bit

CVE-2025-29477Same product: Treasuredata Fluent Bit

Affected Assets

treasuredata

fluent bit

4.1.0

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V5.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can find missing size checks before deployment.

SI-10 Information Input Validation good match

Input validation directly enforces size checks before buffer copies.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles require bounds checking and safe buffer handling in design.

SI-16 Memory Protection partial match

Memory protection limits the impact of an overflow once it occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure development practices directly enforce bounds checking and input validation that prevent classic buffer overflows.

ID.RA-01 partial match

prevents

Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.

PR.PS-02 partial match

prevents

Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match

prevents

Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.

A.8.25 Secure development life cycle partial match

prevents

Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.

A.8.26 Application security requirements partial match

prevents

Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.

A.8.27 Secure system architecture and engineering principles partial match

prevents

Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.