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.
Published: 2026-09-17
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure of feature flag configuration data
Action: Apply Patch
AI Analysis

Impact

A tenant able to deploy a controller‑owned workload can annotate it with the openfeature.dev/featureflagsource annotation using NAMESPACE/NAME syntax. The OpenFeature Operator, in versions 0.9.2 and earlier, reads the referenced FeatureFlagSource or InProcessConfiguration resource from the target namespace and materializes its spec.envVars literal values, spec.httpSyncBearerToken, sync URIs and associated ConfigMaps directly into the tenant’s workload. This allows the tenant to learn sensitive configuration data, including bearer tokens and synchronization endpoints, that were intended to be confined to the target namespace.

Affected Systems

The vulnerability affects the OpenFeature Operator (open-feature:open-feature-operator) version 0.9.2 and earlier when deployed on multi‑tenant Kubernetes clusters that use namespaces as trust boundaries. Single‑tenant clusters are not impacted.

Risk and Exploitability

With a CVSS score of 4.3 and an EPSS score of < 1%, the risk is moderate but the likelihood of exploitation is low. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is a tenant who has permission to create controller‑owned workloads; once such a workload is created, the cluster‑scoped operator reveals the referenced configuration to the tenant. No additional privileges or elevated access are required beyond the ability to create a workload.

Generated by OpenCVE AI on September 18, 2026 at 23:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the OpenFeature Operator to 0.9.3 or later to eliminate cross‑namespace exposure of feature flag data.
  • Restrict RBAC so that tenants cannot create controller‑owned workloads in namespaces where they are not allowed to reference other namespaces’ FeatureFlagSource resources.
  • Audit existing deployments for FeatureFlagSource or InProcessConfiguration annotations that reference external namespaces and remove or neutralize them to prevent accidental data leakage.

Generated by OpenCVE AI on September 18, 2026 at 23:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-398h-7f66-3h4p open-feature-operator: Cross-namespace FeatureFlagSource and InProcessConfiguration resolution exposes spec contents on multi-tenant clusters
History

Sat, 19 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Fri, 18 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Open-feature
Open-feature open-feature-operator
Vendors & Products Open-feature
Open-feature open-feature-operator

Thu, 17 Sep 2026 20:00:00 +0000

Type Values Removed Values Added
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.
Title Cross-namespace FeatureFlagSource and InProcessConfiguration resolution exposes spec contents on multi-tenant clusters
Weaknesses CWE-668
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Subscriptions

Open-feature Open-feature-operator
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-18T14:43:51.856Z

Reserved: 2026-06-15T18:01:15.510Z

Link: CVE-2026-54495

cve-icon Vulnrichment

Updated: 2026-09-18T14:36:50.381Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-17T20:16:50.967

Modified: 2026-09-24T21:20:08.527

Link: CVE-2026-54495

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-18T23:45:15Z

Weaknesses
  • CWE-668

    Exposure of Resource to Wrong Sphere