Vulnerability in Open-Feature Open-Feature-Operator
CVE-2026-54495
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.
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
Affected products
- Open-feature Open-feature-operator — versions <= 0.9.2
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM)
- security-advisories@github.com (x_refsource_MISC)
Frequently asked questions
- What is CVE-2026-54495?
- CVE-2026-54495 is a medium-severity vulnerability in Open-Feature Open-Feature-Operator, classified under Exposure of Resource to Wrong Sphere. CVSS score: 4.3/10. Published 2026-09-17.
- How severe is CVE-2026-54495?
- Medium severity. CVSS v3 base score is 4.3 out of 10.