dbcve.org
Cluster Logging OperatorApplication · Redhat

CVE-2026-10609

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A missing authorization flaw was found in the OpenShift Cluster Logging Operator. The operator creates and forwards ServiceAccount tokens to output destinations without verifying that the ClusterLogForwarder creator has permission to use those credentials, allowing a delegated editor to exfiltrate SA tokens and escalate privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OpenShift Cluster Logging Operator creates and forwards ServiceAccount tokens to log output destinations (e.g., Elasticsearch, Kafka, HTTP) without validating that the ClusterLogForwarder resource creator has permission to access those credentials. A user with delegated editor permissions on a ClusterLogForwarder can trigger the operator to forward SA tokens they shouldn't have access to, enabling token exfiltration and privilege escalation to any service account the operator has access to.

MitigationImplement authorization checks in the ClusterLogForwarder controller to verify the requester has permission to use the target ServiceAccount before creating token references; apply least-privilege RBAC to limit which users can create ClusterLogForwarder resources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cluster Logging OperatorApplication
Affected:all versions
Logging Subsystem For Red Hat OpenshiftApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cluster Logging Operator is installed
    Run `oc get csv -n openshift-logging` or check the OperatorHub for installed operators in the openshift-logging namespace
    Affected if The Cluster Logging Operator or Logging Subsystem for OpenShift is installed in the environment
  2. Identify existing ClusterLogForwarder resources
    Run `oc get ClusterLogForwarder -A` to list all ClusterLogForwarder instances across namespaces
    Affected if Any ClusterLogForwarder resources exist in the cluster
  3. Check who can create ClusterLogForwarder resources
    Run `oc auth can-i create clusterlogforwarders` and examine RBAC bindings with `oc get clusterrolebindings -o wide | grep -i log`
    Affected if Users or groups without full cluster admin privileges have permissions to create ClusterLogForwarder resources
  4. Review ClusterLogForwarder output configurations
    Run `oc get ClusterLogForwarder -A -o yaml` and inspect the `outputs` section for any http, kafka, or elasticsearch destinations that may forward tokens
    Affected if ClusterLogForwarder instances define output destinations that could forward ServiceAccount tokens
  5. Examine the logging operator service account access
    Check the operator's service account in openshift-logging namespace with `oc get sa -n openshift-logging` and review its clusterrole bindings
    Affected if The Cluster Logging Operator's service account has broad access to other service accounts that could be exfiltrated

A user is affected if the Cluster Logging Operator is installed AND users with limited permissions can create or edit ClusterLogForwarder resources that could trigger token forwarding to destinations they shouldn't access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks in the ClusterLogForwarder controller to verify the requester has permission to use the target ServiceAccount before creating token references; apply least-privilege RBAC to limit which users can create ClusterLogForwarder resources.

Fix this in Cluster Logging Operator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10609 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data