kube-logging logging-operator up to 6.5.99 Fluentd configuration renderer fluent.go FluentRender record_transformer.records os command injection

Summaryinfo

A vulnerability has been found in kube-logging logging-operator up to 6.5.99 and classified as very critical. Affected by this vulnerability is the function FluentRender of the file pkg/sdk/logging/model/render/fluent.go of the component Fluentd configuration renderer. Performing a manipulation of the argument record_transformer.records results in os command injection. This vulnerability is cataloged as CVE-2026-54680. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as very critical has been found in kube-logging logging-operator up to 6.5.99. This affects the function FluentRender of the file pkg/sdk/logging/model/render/fluent.go of the component Fluentd configuration renderer. The manipulation of the argument record_transformer.records with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Logging operator automates the deployment and configuration of Kubernetes logging pipelines. Prior to 6.6.0, the Fluentd configuration renderer FluentRender in pkg/sdk/logging/model/render/fluent.go writes CRD strings such as Flow record_transformer.records values directly into fluent.conf without escaping, allowing a user who can create Flow resources to inject a Fluentd <match **> block using @type exec and execute arbitrary commands inside the Fluentd aggregator. This issue is fixed in version 6.6.0.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-54680 since 06/16/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/29/2026). The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

Upgrading to version 6.6.0 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• kube-logging

Name

• logging-operator

Version

• 6.5.0
• 6.5.1
• 6.5.2
• 6.5.3
• 6.5.4
• 6.5.5
• 6.5.6
• 6.5.7
• 6.5.8
• 6.5.9
• 6.5.10
• 6.5.11
• 6.5.12
• 6.5.13
• 6.5.14
• 6.5.15
• 6.5.16
• 6.5.17
• 6.5.18
• 6.5.19
• 6.5.20
• 6.5.21
• 6.5.22
• 6.5.23
• 6.5.24
• 6.5.25
• 6.5.26
• 6.5.27
• 6.5.28
• 6.5.29
• 6.5.30
• 6.5.31
• 6.5.32
• 6.5.33
• 6.5.34
• 6.5.35
• 6.5.36
• 6.5.37
• 6.5.38
• 6.5.39
• 6.5.40
• 6.5.41
• 6.5.42
• 6.5.43
• 6.5.44
• 6.5.45
• 6.5.46
• 6.5.47
• 6.5.48
• 6.5.49
• 6.5.50
• 6.5.51
• 6.5.52
• 6.5.53
• 6.5.54
• 6.5.55
• 6.5.56
• 6.5.57
• 6.5.58
• 6.5.59
• 6.5.60
• 6.5.61
• 6.5.62
• 6.5.63
• 6.5.64
• 6.5.65
• 6.5.66
• 6.5.67
• 6.5.68
• 6.5.69
• 6.5.70
• 6.5.71
• 6.5.72
• 6.5.73
• 6.5.74
• 6.5.75
• 6.5.76
• 6.5.77
• 6.5.78
• 6.5.79
• 6.5.80
• 6.5.81
• 6.5.82
• 6.5.83
• 6.5.84
• 6.5.85
• 6.5.86
• 6.5.87
• 6.5.88
• 6.5.89
• 6.5.90
• 6.5.91
• 6.5.92
• 6.5.93
• 6.5.94
• 6.5.95
• 6.5.96
• 6.5.97
• 6.5.98
• 6.5.99

Website

• Product: https://github.com/kube-logging/logging-operator/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion