Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-54680.

Unlock with Pro - from £29/user/mo
CVE-2026-54680

Kube-logging Logging Operator Fluentd Configuration Injection RCE (CVE-2026-54680)

Detects exploitation of CVE-2026-54680, a critical (CVSS 9.9) configuration injection vulnerability in kube-logging logging-operator (versions prior to the 0.0.0-20260608145523-cf437d7f1e05 pseudo-version / 6.6.0 release) that allows an attacker with the ability to influence Fluentd/Fluent Bit configuration inputs (e.g. via Flow/ClusterFlow/Output CRDs, log forwarding pipelines, or unsanitized log fields reflected into config templates) to inject arbitrary Fluentd configuration directives. This injection can lead to remote code execution via Fluentd's exec plugin, ruby code blocks, or file-based output writes, potentially compromising the logging-operator pod and any Kubernetes service account/token it holds, enabling lateral movement and cluster compromise.

Vulnerability Intelligence

Public PoC

CVSS

9.9
Critical (9.0–10)

CVSS vector not yet published

Write-up coming soon

What is CVE-2026-54680 Kube-logging Logging Operator Fluentd Configuration Injection RCE (CVE-2026-54680)?

Kube-logging Logging Operator Fluentd Configuration Injection RCE (CVE-2026-54680) (CVE-2026-54680) maps to the Initial Access and Execution and Privilege Escalation and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Kube-logging Logging Operator Fluentd Configuration Injection RCE (CVE-2026-54680), covering the data sources and telemetry it touches: Kubernetes Audit Logs, Container Logs, Azure Kubernetes Service Diagnostic Logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Privilege Escalation Lateral Movement
Microsoft Sentinel / Defender
kusto
let SuspiciousFluentdDirectives = dynamic(["exec", "exec_filter", "script", "ruby", "system(", "`", "| sh", "| bash", "/bin/sh", "/bin/bash"]);
KubernetesConfigLog
| where TimeGenerated > ago(24h)
| where PodName has_any ("logging-operator", "fluentd", "fluent-bit")
| where ObjectKind in ("Flow", "ClusterFlow", "Output", "ClusterOutput", "Logging")
| where OperationType in ("create", "update", "patch")
| extend ConfigContent = tostring(RequestObject)
| where ConfigContent has_any (SuspiciousFluentdDirectives)
| project TimeGenerated, PodName, Namespace, ObjectKind, UserAgent, RequestingUser=RequestObject.metadata.managedFields, ConfigContent
| union (
ContainerLogV2
| where TimeGenerated > ago(24h)
| where PodName has_any ("logging-operator", "fluentd", "fluent-bit")
| where LogMessage has_any (SuspiciousFluentdDirectives) or LogMessage has "invalid configuration" or LogMessage has "parse error"
| project TimeGenerated, PodName, Namespace, ConfigContent=LogMessage
)
| order by TimeGenerated desc

Detects Kubernetes audit log entries and container logs showing suspicious Fluentd directive injection (exec, script, ruby blocks, shell metacharacters) written to Flow/ClusterFlow/Output custom resources or observed in logging-operator/fluentd pod logs, indicative of CVE-2026-54680 exploitation.

critical severity medium confidence

Data Sources

Kubernetes Audit Logs Container Logs Azure Kubernetes Service Diagnostic Logs

Required Tables

KubernetesConfigLog ContainerLogV2

False Positives

  • Legitimate use of exec/script output plugins by cluster admins for approved log processing pipelines
  • Internal security tooling that intentionally references shell-like strings in log messages for testing
  • Fluentd configuration validation errors unrelated to malicious injection
  • Third-party log forwarders with legitimate ruby filter plugins in use

Sigma rule & cross-platform mapping

The detection logic for Kube-logging Logging Operator Fluentd Configuration Injection RCE (CVE-2026-54680) (CVE-2026-54680) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  product: azure

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Inject exec directive via ClusterFlow CRD

    Expected signal: Kubernetes audit log entries for create operations on ClusterFlow and ClusterOutput resources containing an 'exec' block, followed by fluentd operator reconciliation logs regenerating the rendered configuration.

  2. Test 2Inject ruby eval block into Output configuration

    Expected signal: Audit log capturing the Output resource creation with enableRuby=true and a system() call embedded in the record template; fluentd pod logs showing plugin reconfiguration.

  3. Test 3Simulate command execution artifact from compromised fluentd pod

    Expected signal: Container runtime/EDR process execution events for /bin/sh, id, whoami, and cat commands executed inside the fluentd pod, plus Kubernetes audit log entry for the 'pods/exec' subresource.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-54680 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections