Open Feature Operator
Approved changes feed: RSS · Atom
cpe:2.3:a:open-feature:open-feature-operator:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Open Feature (4ae102c4-457f-5206-a37d-f166f0e47fbf) |
|---|---|
| Product | Open Feature Operator (79a1ea80-0641-5057-ad9b-773ef67aa06b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54495 |
vulnerable | 2026-10-13 12:29:13.796114 |
Cross-namespace FeatureFlagSource and InProcessConfiguration resolution exposes spec contents on multi-tenant clusters
MEDIUM (4.3)
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-17T19:44:13.222Z
Updated: 2026-09-18T14:43:51.856Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-29018 |
vulnerable | 2026-06-08 06:02:37.941448 |
OpenFeature Operator vulnerable to Cluster-level Privilege Escalation
HIGH (8.1)
The OpenFeature Operator allows users to expose feature flags to applications. Assuming the pre-existence of a vulnerability that allows for arbitrary code execution, an attacker could leverage the lax permissions configured on `open-feature-operator-controller-manager` to escalate the privileges of any SA in the cluster. The increased privileges could be used to modify cluster state, leading to DoS, or read sensitive data, including secrets. Version 0.2.32 mitigates this issue by restricting the resources the `open-feature-operator-controller-manager` can modify.
Published: 2023-04-14T18:47:03.747Z
Updated: 2025-02-06T18:42:47.890Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.