Out-of-directory file writes via unsanitized tag paths
Published Nov 24, 2025 · Updated Jan 7, 2026
Path traversal in Fluent Bit before 4.0.12 allows remote attackers to write files outside the configured directory via crafted tags. When the out_file plugin's File option is omitted, its flush path uses the untrusted record tag as a filename without sanitizing traversal segments. Exposure requires a network-reachable input that lets an attacker control tags and an out_file output lacking File; successful exploitation alters files writable by the Fluent Bit process.
Summary
What happened
Path traversal in Fluent Bit before 4.0.12 allows remote attackers to write files outside the configured directory via crafted tags. When the out_file plugin's File option is omitted, its flush path uses the untrusted record tag as a filename without sanitizing traversal segments. Exposure requires a network-reachable input that lets an attacker control tags and an out_file output lacking File; successful exploitation alters files writable by the Fluent Bit process.
The record
- CVE
- CVE-2025-12972
- Published
- Nov 24, 2025
- Updated
- Jan 7, 2026
- Vendor
- Fluent Bit
- Product
- Fluent Bit
- Classifications
- CWE-35, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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.
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