CVE-2025-12977
Treasuredata Fluent Bit 4.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-12977 is a critical-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Treasuredata Fluent Bit. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 50% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to 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-12977 is a high-severity vulnerability (CVSS 9.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) affecting the Fluent Bit data collection and forwarding agent, specifically its in_http, in_splunk, and in_elasticsearch input plugins. These plugins fail to properly sanitize tag_key inputs, allowing attackers to inject special characters such as newlines or path traversal sequences like "../". Tags in Fluent Bit influence record routing and are used by some output plugins to derive filenames or contents, enabling impacts like newline injection, path traversal, forged record injection, or log misrouting, which compromise data integrity and routing (CWE-1287).
Attackers with network access to the affected Fluent Bit instance or the ability to write records into connected Splunk or Elasticsearch systems can exploit this remotely with low complexity and no privileges required. By supplying malicious tag_key values via HTTP, Splunk, or Elasticsearch inputs, they can manipulate tag processing to inject arbitrary newlines into logs, traverse paths in file-based outputs, forge records that appear to originate from other sources, or redirect logs to unintended destinations, potentially leading to widespread log corruption or exposure of sensitive data.
The official Fluent Bit advisory details that these vulnerabilities have been addressed in version 4.1, with backports available for version 4.0. Security practitioners should update to these patched releases and review configurations for exposed input plugins, particularly in cloud environments where Fluent Bit is commonly deployed for log aggregation. Additional analysis from Oligo Security highlights the risk of remote takeover in such setups.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-198811
Vulnerability Data
Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with network access or the ability to write records into Splunk or Elasticsearch can supply tag_key values containing special characters such as newlines or ../…
more
that are treated as valid tags. Because tags influence routing and some outputs derive filenames or contents from tags, this can allow newline injection, path traversal, forged record injection, or log misrouting, impacting data integrity and log routing.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.1V1.4.2V2.1.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.
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.
Secure SDLC practices directly require proper input type validation during development.
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.
Security testing can detect type-validation flaws but does not prevent them during development.
Secure development lifecycle mandates input validation and type checking to prevent improper type handling.
Application security requirements explicitly include validation of input data types and formats.
Secure architecture principles promote defensive input handling and type enforcement at system boundaries.
Secure coding standards directly require proper type validation of all external inputs.