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

> A tenant can read sensitive configuration data from other namespaces by referencing cross-namespace resources in multi-tenant clusters.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-398h-7f66-3h4p, GO-2026-5998

## What is CVE-2026-54495?

CVE-2026-54495 is a medium-severity vulnerability in open-feature-operator, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2026-54495?

3 open source packages ship an affected version, including github.com/open-feature/open-feature-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/open-feature/open-feature-operator` | Go | All versions | None |
| `github.com/open-feature/open-feature-operator` | Go | All versions to 0.9.2 | None |
| `github.com/open-feature/open-feature-operator` | Go | All versions to 0.9.2 | None |

## How do I fix CVE-2026-54495?

Upgrade to a fixed version.

## Is CVE-2026-54495 being exploited?

There is no known exploitation of CVE-2026-54495 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54495 and fix it if it is affected.

What it is: CVE-2026-54495 is a medium-severity vulnerability in open-feature-operator, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54495 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/open-feature/open-feature-operator (Go): affected all versions; no fix listed
- github.com/open-feature/open-feature-operator (Go): affected all versions up to 0.9.2; no fix listed
- github.com/open-feature/open-feature-operator (Go): affected all versions up to 0.9.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54495/ (Markdown: https://insights.sbomify.com/CVE-2026-54495/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54495
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54495
- OSV: https://osv.dev/vulnerability/CVE-2026-54495

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54495/
Summaries are generated and may contain mistakes; the official description above is the record.