Information Exposure Affecting opentelemetry-operator-otel-allocator package, versions <0.152.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-OPENTELEMETRYOPERATOROTELALLOCATOR-17312201
- published12 Jun 2026
- disclosed14 Sept 2026
Introduced: 12 Jun 2026
CVE-2026-47701 (opens in a new tab)How to fix?
Upgrade Minimos:latest opentelemetry-operator-otel-allocator to version 0.152.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream opentelemetry-operator-otel-allocator package and not the opentelemetry-operator-otel-allocator package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
The OpenTelemetry Operator is a Kubernetes Operator for the OpenTelemetry Collector. Prior to 0.152.0, cmd/otel-allocator TargetAllocator instances with targetAllocator.prometheusCR.enabled set to true preserve a selected ServiceMonitor endpoint's bearerTokenFile value as HTTPClientConfig.Authorization.CredentialsFile. A tenant who can create or update a ServiceMonitor matched by serviceMonitorSelector and serviceMonitorNamespaceSelector can point bearerTokenFile at a file in the Collector pod, including /var/run/secrets/kubernetes.io/serviceaccount/token, and direct scraping to a tenant-controlled endpoint. The Collector reads that file at scrape time and sends its contents as bearer authorization on every scrape interval. Exploitation also requires the Collector service-account token or another sensitive file to be mounted and the Collector to reach the chosen target. The DenyFSAccessThroughSMs control was absent, allowing disclosure of the Collector's service-account JWT or other mounted files, and resulting Kubernetes API impact is limited by the Collector service account's permissions. This issue is fixed in version 0.152.0.
References
- https://www.cve.org/CVERecord?id=CVE-2026-47701
- https://github.com/advisories/GHSA-cxh2-4639-vmc5
- https://osv.dev/vulnerability/MINI-pphx-346g-j59h
- https://osv.dev/vulnerability/CVE-2026-47701
- https://github.com/open-telemetry/opentelemetry-operator/commit/95a8c2a3dc64a762d3ab8eba8c903b5702a03a9c
- https://github.com/open-telemetry/opentelemetry-operator/pull/5104
- https://github.com/open-telemetry/opentelemetry-operator/releases/tag/v0.152.0
- https://github.com/open-telemetry/opentelemetry-operator/security/advisories/GHSA-cxh2-4639-vmc5