Loading story…
Five critical vulnerabilities were discovered in Fluent Bit, a widely used open-source telemetry and log collection agent deployed across major cloud providers and AI labs. These flaws, some of which have existed for years, allow attackers to bypass authentication, perform path traversal, achieve remote code execution, cause denial-of-service, and manipulate log tags. The vulnerabilities, identified by Oligo Security, affect all major cloud platforms and have the potential to disrupt cloud services, alter or tamper with data, and enable deeper intrusions into cloud and Kubernetes infrastructure. Fluent Bit is used by tech giants such as Google, Amazon, Oracle, IBM, Microsoft, and OpenAI, with over 15 billion deployments worldwide.
The vulnerabilities include CVE-2025-12972 (path traversal via unsanitized tag values), CVE-2025-12970 (stack buffer overflow in the Docker Metrics input plugin), CVE-2025-12978 (tag-matching logic spoofing), CVE-2025-12977 (improper input validation of tags), and CVE-2025-12969 (missing authentication in the in_forward plugin). Exploiting these flaws could allow attackers to write or overwrite arbitrary files, inject malicious records, reroute logs, and flood security products with false events. The issues have been addressed in Fluent Bit versions v4.1.1 and 4.0.12, and users are urged to update immediately to mitigate risk.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
An oss-sec mailing list post summarized the five newly disclosed Fluent Bit CVEs, including path traversal, stack buffer overflow, tag spoofing, sanitization bypass, and authentication disablement issues. The post also cited Fluent Bit's advisory stating the vulnerabilities were fixed in v4.2 and v4.1.1 and backported to v4.0.14.
Coordinated disclosure involved AWS, and CERT/CC noted that several of the flaws require network access to a Fluent Bit instance and could lead to authentication bypass, RCE, service disruption, and tag spoofing. AWS advised customers using Fluent Bit to update to patched versions.
Oligo Security disclosed five long-standing vulnerabilities in Fluent Bit that can enable authentication bypass, tag manipulation, path traversal, denial of service, and potential remote code execution. The researchers warned the bugs could be chained to tamper with logs, overwrite files, and compromise cloud and Kubernetes environments.
Fluent Bit addressed five security flaws in stable releases published last month, with fixes available in versions 4.1.1 and 4.0.12 according to coordinated disclosure reporting. A later advisory and oss-sec post indicated the fixes were also present in v4.2 and backported to v4.0.14.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourcescworld.com
Open sourcego.theregister.com
Open sourcethehackernews.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity flaw tracked as **`CVE-2026-54680`** allows remote code execution in the `kube-logging/logging-operator` before version **6.6.0** by injecting malicious content into generated Fluentd configuration. The bug is in the `FluentRender` component, which writes CRD-supplied strings directly into `fluent.conf` without properly escaping special characters. Attackers with permission to create **Flow** or **ClusterFlow** resources can abuse fields such as `record_transformer.records` to break out of nested configuration blocks and insert arbitrary top-level Fluentd directives. By injecting a crafted `<match **>` block and using plugins such as **`@type exec`**, an attacker can execute arbitrary commands inside the Fluentd aggregator when logs are processed. The vulnerability is classified as command injection and configuration injection, mapped to **`CWE-77`** and **`CWE-74`**, with CVSS v3.1 **`AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`**. Maintainers fixed the issue in **logging-operator 6.6.0** by escaping newline, carriage return, tab, quote, backslash, and `#` characters, while defenders were also provided a Kyverno policy example to block newline characters in vulnerable record fields as a mitigation.
Jul 30, 2026
IBM disclosed five high-severity vulnerabilities in **Langflow OSS** affecting versions `1.0.0` through `1.10.0`, including multiple paths to **remote code execution**, privilege escalation, and arbitrary file write. The issues are tracked as `CVE-2026-9135`, `CVE-2026-8476`, `CVE-2026-8481`, `CVE-2026-8635`, and `CVE-2026-8859`. Reported weaknesses include code injection through unvalidated dynamic `CodeInput` fields in the Policies component, unsafe `pickle.loads()` deserialization in the disk cache, direct execution of user-supplied Python in the `/api/v1/validate/code` endpoint, database manipulation that can elevate an authenticated user to superuser, and path traversal in the APIRequest component's **Save to File** feature via crafted `Content-Disposition` filenames. Several of the flaws require only authenticated access and can lead to arbitrary Python or system command execution with the privileges of the Langflow server process, creating a path to full host compromise in some deployments. IBM released **Langflow OSS `1.10.1`** to address all five vulnerabilities and advised organizations to upgrade immediately; additional mitigation guidance includes reviewing file-system permissions and sanitizing or removing cached data where possible. Public reporting said no active exploitation had been confirmed at publication time.
Jul 19, 2026
Multiple vulnerabilities in **Langflow** have exposed AI application deployments to both account-to-account abuse and active compromise. **`CVE-2026-33760`** affects versions before **1.9.0** and allows authenticated users to read, modify, rename, or delete other users’ messages, sessions, build artifacts, and LLM transaction logs through seven `/api/v1/monitor` endpoints that fail to enforce ownership checks. A separate flaw, **`CVE-2026-55255`**, affects versions before **1.9.2** and lets an authenticated attacker execute another user’s flow through the `/api/v1/responses` endpoint by supplying a victim `flow_id`, giving the issue a critical **CVSS 9.9** rating. At the same time, defenders are tracking a cryptocurrency-mining campaign exploiting **`CVE-2026-33017`**, an unauthenticated remote code execution bug in Langflow, to compromise exposed instances and deploy Monero miners. Threat research says the malware disables security controls, installs persistence, and can enable lateral movement through reused SSH keys; observed infrastructure includes **`83.142.209.214`** and **`94.156.64.241`**. Organizations running Langflow are being urged to upgrade to **1.9.0** and **1.9.2** or later as applicable, verify access-control enforcement, restrict public exposure of Langflow services, and treat signs of miner activity or unauthorized flow execution as a significant incident.
Jun 30, 2026