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 block using @type exec and execute arbitrary commands inside the Fluentd aggregator. This issue is fixed in version 6.6.0.
CVE-2026-54680
CRITICALPre-NVD 9.99.9—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 61(Track*)EG Risk 61/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 30, 2026
Advisory Details (3)
Auto-updated Jul 30, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github Patch Available🟡 PoC Available
Fluentd configuration injection in Logging operator allows remote code execution · Advisory · kube-logging/logging-operator · GitHub
https://github.com/kube-logging/logging-operator/security/advisories/GHSA-mjqf-28ph-426hgithub_release Patch Available
6.6.0
Patch available: kube-logging/logging-operator 6.6.0
https://github.com/kube-logging/logging-operator/releases/tag/6.6.0github_commit Patch Available
commit cf437d7f1e05 (kube-logging/logging-operator)
Patch available: kube-logging/logging-operator 6.6.0 (contains commit cf437d7f1e05)
https://github.com/kube-logging/logging-operator/commit/cf437d7f1e056c78740bf5716ac8bdebcf002425Vendor Advisories for CVE-2026-54680(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/kube-logging/logging-operator | — | 0.0.0-20260608145523-cf437d7f1e05 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 18:45 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 14:38 UTCEG score recompute
- 2026-07-30 14:08 UTCEG score recompute
- 2026-07-30 12:14 UTCEG score recompute
- 2026-07-29 17:26 UTCEG score recompute
- 2026-07-29 17:08 UTCEG score recompute
- 2026-07-29 17:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77 · CWE-74
Frequently asked(5)
What is CVE-2026-54680?
CVE-2026-54680 is a critical vulnerability published on July 29, 2026. 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…
When was CVE-2026-54680 disclosed?
CVE-2026-54680 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54680 actively exploited?
CVE-2026-54680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54680?
CVE-2026-54680 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-54680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54680
Is Your Infrastructure Affected by CVE-2026-54680?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.