How severe is CVE-2025-12970?

CVE-2025-12970 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-12970 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-12970?

CVE-2025-12970 affects Treasuredata Fluent Bit. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-12970?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-12970 have an EU (EUVD) identifier?

Yes. CVE-2025-12970 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198809.

When was CVE-2025-12970 published?

CVE-2025-12970 was published on 2025-11-24 and last updated on 2026-06-17.

CVE-2025-12970

CVE-2025-12970 is a high-severity vulnerability in Treasuredata Fluent Bit with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-120.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-198809
Weakness: CWE-120
Affected product: Treasuredata Fluent Bit
Published: 2025-11-24
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-12970?: 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.
How severe is CVE-2025-12970?: CVE-2025-12970 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-12970 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-12970?: CVE-2025-12970 affects Treasuredata Fluent Bit. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-12970?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-12970 have an EU (EUVD) identifier?: Yes. CVE-2025-12970 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198809.
When was CVE-2025-12970 published?: CVE-2025-12970 was published on 2025-11-24 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:treasuredata:fluent_bit:4.1.0:*:*:*:*:*:*:*

More vulnerabilities in Treasuredata Fluent Bit

CVE-2024-4323 — Critical (CVSS 9.8): A memory corruption vulnerability in Fluent Bit versions 2.0.7 thru 3.0.3. This issue lies in the embedded http…
CVE-2021-36088 — Critical (CVSS 9.8): Fluent Bit (aka fluent-bit) 1.7.0 through 1.7.4 has a double free in flb_free (called from flb_parser_json_do and…
CVE-2025-12977 — Critical (CVSS 9.1): Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with…
CVE-2021-46879 — High (CVSS 7.8): An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data resulting…
CVE-2021-46878 — High (CVSS 7.8): An issue was discovered in Treasure Data Fluent Bit 1.7.1, erroneous parsing in flb_pack_msgpack_to_json_format leads…
CVE-2020-35963 — High (CVSS 7.8): flb_gzip_compress in flb_gzip.c in Fluent Bit before 1.6.4 has an out-of-bounds write because it does not use the…

All CVEs affecting Treasuredata Fluent Bit →

Other CWE-120 (Classic Buffer Overflow) vulnerabilities

CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2026-24823 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in FASTSHIFT…
CVE-2026-24810 — Critical (CVSS 10.0): Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in rethinkdb (src/cjson modules).…
CVE-2026-24800 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in tildearrow…
CVE-2025-9962 — Critical (CVSS 10.0): A buffer overflow vulnerability in Novakon P series allows attackers to gain root permission without prior…
CVE-2010-10016 — Critical (CVSS 10.0): BS.Player version 2.57 (build 1051) contains a vulnerability in its playlist import functionality. When processing .m3u…

Browse all CWE-120 (Classic Buffer Overflow) vulnerabilities →