# CVE-2026-54680: Logging operator has Fluentd configuration injection that allows remote code execution

> Attackers with Flow creation permissions can inject Fluentd configuration to execute arbitrary commands in the aggregator.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-mjqf-28ph-426h, GO-2026-6142, MINI-c369-jg4r-mpwx, MINI-rfpc-v9g6-8qhw

## What is CVE-2026-54680?

CVE-2026-54680 is a critical code injection vulnerability in kube-logging logging-operator, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-54680?

3 open source packages ship an affected version, including github.com/kube-logging/logging-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kube-logging/logging-operator` | Go | All versions | 0.0.0-20260608145523-cf437d7f1e05 |
| `github.com/kube-logging/logging-operator` | Go | All versions | 0.0.0-20260608145523-cf437d7f1e05 |
| `github.com/kube-logging/logging-operator` | Go | All versions | 0.0.0-20260608145523-cf437d7f1e05 |

## How do I fix CVE-2026-54680?

Upgrade github.com/kube-logging/logging-operator to 0.0.0-20260608145523-cf437d7f1e05 or later.

## Is CVE-2026-54680 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54680 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54680 and fix it if it is affected.

What it is: CVE-2026-54680 is a critical code injection vulnerability in kube-logging logging-operator, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54680 exists.

Affected packages and fixed versions:
- github.com/kube-logging/logging-operator (Go): affected all versions; fixed in 0.0.0-20260608145523-cf437d7f1e05
- github.com/kube-logging/logging-operator (Go): affected all versions; fixed in 0.0.0-20260608145523-cf437d7f1e05
- github.com/kube-logging/logging-operator (Go): affected all versions; fixed in 0.0.0-20260608145523-cf437d7f1e05

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54680/ (Markdown: https://insights.sbomify.com/CVE-2026-54680/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54680
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54680
- OSV: https://osv.dev/vulnerability/CVE-2026-54680

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54680/
Summaries are generated and may contain mistakes; the official description above is the record.