Loading story…
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.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-54680 was publicly described as a Fluentd configuration injection vulnerability in logging-operator's FluentRender component. The disclosure states that an attacker able to create Flow resources can inject a Fluentd <match **> block using @type exec and execute arbitrary commands inside the Fluentd aggregator.
A command injection vulnerability in kube-logging logging-operator affecting versions earlier than 6.6.0 was fixed in version 6.6.0. The patch escapes special characters in Fluentd configuration rendering to prevent CRD-supplied values from injecting arbitrary Fluentd directives and achieving remote code execution.
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.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvereports.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.
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.
Jun 29, 2026
Flowise disclosed a critical remote code execution flaw, tracked as **`CVE-2026-56274`**, affecting versions before **`3.1.2`** in the Custom MCP Server feature. The vulnerability stems from multiple OS command injection paths in **`validateCommandFlags`** and **`validateArgsForLocalFileAccess`**, allowing attackers to configure a malicious MCP server and execute arbitrary commands on the Flowise host. The issue is rated **CVSS 9.9** and is remotely exploitable. Advisories describe three bypass techniques: an incomplete Docker argument blocklist that permits **`docker build`** with a remote URL, an **`npx`** blocklist bypass where **`--yes`** is allowed even though **`-y`** is blocked, and a Unix path validation weakness that lets paths beginning with **`//`** evade local file access checks for **`node`**. Exploitation requires any Flowise account role or API access with view and update permissions for chatflows. Organizations were urged to upgrade to **`Flowise 3.1.2`** or later, review MCP server configurations, and restrict chatflow management permissions.
Jun 29, 2026
A high-severity flaw tracked as **CVE-2026-61459** affects Flux159's **mcp-server-kubernetes** before version **3.9.0**, allowing argument injection in the structured tools `kubectl_get`, `kubectl_describe`, and `kubectl_delete`. Attackers can supply `resourceType` or `name` values beginning with dashes to bypass the project's `assertNoDangerousFlags` check and inject flags such as `--server`, redirecting `kubectl` requests to an attacker-controlled Kubernetes API endpoint. The redirection can cause the operator's bearer token to be transmitted externally and could lead to full Kubernetes cluster compromise. Flux159 addressed the issue in version **3.9.0** with a hardening patch that adds argv-wide validation through `assertSafeArgv` and a guarded execution wrapper, replacing direct command execution across affected `kubectl` and `helm` modules while also blocking dangerous kube-related flags that could alter API server or credential handling.
Jul 11, 2026