CVE-2026-54680

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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
Elevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 29, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Sep 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
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-426h
github_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.0
github_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/cf437d7f1e056c78740bf5716ac8bdebcf002425

Vendor 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)
PackageVulnerable rangeFixed inDependents
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 10× in last 7d / 49× 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.

  1. 2026-09-15 07:50 UTCEG score recompute
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-13 19:53 UTCEG score recompute
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 16:11 UTCEG score recompute
  6. 2026-09-11 15:06 UTCEG score recompute
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 13:04 UTCEG score recompute
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-09 07:47 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 20:46 UTCEG score recompute
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 14:16 UTCEG score recompute
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:06 UTCEG score recompute
  17. 2026-09-04 16:17 UTCEG score recompute
  18. 2026-09-04 11:55 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 22:46 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-30 21:40 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 64 more
  1. 2026-08-30 03:00 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 23:17 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 20:55 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 19:39 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 17:38 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 15:13 UTCEG score recompute
  12. 2026-08-24 11:30 UTCEG score recompute
  13. 2026-08-23 01:58 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:58 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 01:37 UTCEG score recompute
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 19:38 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 18:35 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 16:55 UTCEG score recompute
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 18:02 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 03:11 UTCEG score recompute
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 04:54 UTCEG score recompute
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-13 23:10 UTCEG score recompute
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 17:27 UTCEG score recompute
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 15:29 UTCEG score recompute
  36. 2026-08-11 00:38 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 15:10 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 16:54 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 18:38 UTCEG score recompute
  43. 2026-08-06 16:35 UTCEG score recompute
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 22:01 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 16:14 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 12:31 UTCEG score recompute
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-03 12:00 UTCEG score recompute
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-02 02:36 UTCEG score recompute
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 04:19 UTCEG score recompute
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 18:45 UTCEG score recompute
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 14:38 UTCEG score recompute
  60. 2026-07-30 14:08 UTCEG score recompute
  61. 2026-07-30 12:14 UTCEG score recompute
  62. 2026-07-29 17:26 UTCEG score recompute
  63. 2026-07-29 17:08 UTCEG score recompute
  64. 2026-07-29 17:07 UTCMITRE cvelistV5first tracked

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 September 10, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% 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

Explore →

Is Your Infrastructure Affected by CVE-2026-54680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs