Fedora Account System
Red Hat Associate
Red Hat Customer
The destination namespace in the local cluster is taken directly from a label/annotation on the broker object — fully attacker-controlled. The lighthouse-agent SA (which holds cluster-wide create/update on endpointslices and serviceimports per operator RBAC) then writes the object into that namespace on behalf of the remote cluster. There is no allowlist, no check that the namespace exists locally with matching ownership, and no check that the source cluster was authorized to export that {namespace, name}. A compromised spoke can inject EndpointSlices and ServiceImports into any namespace on peer clusters, including kube-system and openshift-* namespaces. Source: Project Glasswing AI-SAST audit of submariner-io/lighthouse. Finding ID: FIND-002 Assurance: execution_proven
ACTION NEEDED: All 19 Jira trackers (ACM-38531 through ACM-38549) were closed as Duplicate of ACM-38761 on 2026-09-02. ACM-38761 is the engineering fix tracker (commit a48019dcac5c5f0fc2dd051e00544e0f66ac8ba9, Resolved/Done 2026-09-09, assignee Thomas Pantelis). However, the fix was NOT tied to an RHSA advisory, so the CVE page shows no fix status. To properly close this CVE on the public-facing page, the ACM team needs to: 1. Reopen the per-stream security trackers (or file new ones) 2. Include CVE-2026-66788 in a Konflux Release CR with type: RHSA for each affected stream (rhacm-2.13.z, 2.14, 2.15, 2.16, 2.17) 3. Once the RHSA ships, the trackers will be linked to the errata and the CVE page will reflect the fix Affected components: lighthouse-agent-rhel9, lighthouse-coredns-rhel9, subctl-rhel9, submariner-rhel9-operator Fix reference: ACM-38761 (https://redhat.atlassian.net/browse/ACM-38761)