Unrated

Cross-namespace information disclosure in open-feature-operator

IdentifiersCVE-2026-54495CWE-668

CVE-2026-54495 is an information disclosure vulnerability in open-feature-operator caused by implicit cross-namespace resolution of FeatureFlagSource and InProcessConfiguration resources. In multi-tenant Kubernetes environments where namespaces are used as trust boundaries, a tenant with permission to create a controller-owned workload in its own namespace can reference another namespace's FeatureFlagSource or InProcessConfiguration. The operator may then materialize the referenced resource's spec contents into the attacker's workload, exposing inline configuration data that should remain isolated to the source namespace. Exposed data can include inline environment variable values, bearer tokens used for HTTP synchronization, and synchronization URIs. The issue stems from improper isolation of resources across namespaces rather than a failure of Kubernetes secret namespace enforcement itself.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a tenant in a multi-tenant cluster to read sensitive configuration data belonging to another tenant by causing the operator to project or materialize that data into resources under the attacker's control. This can disclose inline configuration values, authentication material such as HTTP sync bearer tokens, and service endpoint information. The vulnerability breaks namespace-based isolation assumptions and can enable follow-on abuse such as unauthorized access to downstream services or environments that trust the disclosed credentials. Single-tenant clusters are not impacted according to the available information.

Mitigation

If you can’t patch tonight, do this now.

Avoid storing plaintext secrets or other sensitive values directly in FeatureFlagSource or InProcessConfiguration spec fields. Treat custom resource specification contents as potentially readable by anyone able to trigger operator processing of those resources. Prefer secret references such as valueFrom.secretKeyRef instead of inline environment variable values so Kubernetes same-namespace secret resolution is enforced by the kubelet. Do not embed credentials in synchronization source URIs. Where feasible, restrict create permissions on affected custom resources and on controller-owned workloads through RBAC, especially in clusters where namespaces are intended to enforce tenant boundaries.

Remediation

Patch, then assume compromise.

Upgrade to a release that introduces explicit cluster-scoped CRDs, including ClusterFeatureFlagSource and ClusterInProcessConfiguration, and removes implicit cross-namespace resolution behavior. Until such a release is deployed, rework operator usage patterns so that sensitive values are not stored inline in FeatureFlagSource or InProcessConfiguration specifications, and review RBAC to limit which principals can create the affected custom resources and controller-owned workloads in environments that rely on namespace separation for tenant isolation.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity