Vulnerability · Published Sep 17, 2026 · Assigned by GitHub_M

CVE-2026-54495Cross-namespace FeatureFlagSource and InProcessConfiguration resolution exposes spec contents on multi-tenant clusters

Medium 4.3

In plain English

A medium-severity security flaw in open-feature-operator from open-feature. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities).

Severity (CVSS 3.1)4.3Medium

Exploit odds (30 days)0.3%top 76.5% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

The OpenFeature Operator allows users to expose feature flags to applications. In version 0.9.2 and earlier, a tenant who can create a controller-owned workload can use the openfeature.dev/featureflagsource annotation with NAMESPACE/NAME syntax to reference a FeatureFlagSource or InProcessConfiguration in another namespace. On multi-tenant clusters that use namespaces as trust boundaries, the cluster-scoped operator reads that resource and materializes spec.envVars literal values, spec.httpSyncBearerToken, sync URIs, and supporting ConfigMaps into the tenant's workload. Single-tenant clusters are not impacted, secretKeyRef and configMapKeyRef values remain namespace-local, and creating a FeatureFlagSource is not required.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
Go	github.com/open-feature/open-feature-operator	no fix listed	GHSA-398h-7f66-3h4p
Go	github.com/open-feature/open-feature-operator	no fix listed	GO-2026-5998

Affected products (as reported)

Vendor	Product	Versions
open-feature	open-feature-operator	<= 0.9.2

Weakness: CWE-668 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

https://github.com/open-feature/open-feature-operator/security/advisories/GHSA-398h-7f66-3h4p x_refsource_CONFIRM
https://github.com/open-feature/open-feature-operator/issues/847 x_refsource_MISC