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 ../ 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.
References
Configurations
History
28 Nov 2025, 18:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
|
28 Nov 2025, 15:23
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:treasuredata:fluent_bit:4.1.0:*:*:*:*:*:*:* | |
| First Time |
Treasuredata fluent Bit
Treasuredata |
|
| References | () https://fluentbit.io/announcements/v4.1.0/ - Release Notes |
24 Nov 2025, 20:15
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.1 |
| CWE | CWE-1287 |
24 Nov 2025, 15:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-11-24 15:15
Updated : 2025-11-28 18:15
NVD link : CVE-2025-12977
Mitre link : CVE-2025-12977
CVE.ORG link : CVE-2025-12977
JSON object : View
Products Affected
treasuredata
- fluent_bit
CWE
CWE-1287
Improper Validation of Specified Type of Input
