CVE-2026-54495: CWE-668: Exposure of Resource to Wrong Sphere in open-feature open-feature-operator

The OpenFeature Operator enables users to expose feature flags to applications. In versions 0.9.2 and earlier, a tenant who can create a controller-owned workload can exploit the openfeature.dev/featureflagsource annotation with NAMESPACE/NAME syntax to reference FeatureFlagSource or InProcessConfiguration resources in other namespaces. On multi-tenant clusters using namespaces as trust boundaries, the operator reads these cross-namespace resources and materializes sensitive data such as spec.envVars literal values, spec.httpSyncBearerToken, sync URIs, and supporting ConfigMaps into the tenant's workload. This results in exposure of resources across tenant boundaries. Single-tenant clusters are not impacted, and secretKeyRef and configMapKeyRef values remain confined to their namespaces. Creating a FeatureFlagSource is not required for exploitation.

In multi-tenant Kubernetes clusters that use namespaces as trust boundaries, this vulnerability allows a tenant with limited privileges to access environment variables, bearer tokens, sync URIs, and ConfigMaps from other tenants' namespaces. This exposure can lead to information disclosure across tenant boundaries. The impact is limited to confidentiality (C:L), with no integrity or availability impact reported. Single-tenant clusters are not affected.

No official patch or fix is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators of multi-tenant clusters should consider restricting the ability of tenants to create controller-owned workloads or to use the openfeature.dev/featureflagsource annotation referencing other namespaces. Single-tenant clusters are not impacted by this issue.