Information Exposure Affecting github.com/open-telemetry/opentelemetry-operator/apis package, versions <0.152.0
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-GOLANG-GITHUBCOMOPENTELEMETRYOPENTELEMETRYOPERATORAPIS-17735315
- published30 Jun 2026
- disclosed10 Jun 2026
- creditUnknown
Introduced: 10 Jun 2026
CVE-2026-47701 Â (opens in a new tab)How to fix?
Upgrade github.com/open-telemetry/opentelemetry-operator/apis to version 0.152.0 or higher.
Overview
Affected versions of this package are vulnerable to Information Exposure via the bearerTokenFile field in the ServiceMonitor resource. An attacker can exfiltrate sensitive files from the pod filesystem by configuring a ServiceMonitor to reference arbitrary files and directing the scrape target to an endpoint under their control. This is only exploitable if the OpenTelemetry Collector is deployed with targetAllocator.prometheusCR.enabled set to true, the serviceMonitorSelector or serviceMonitorNamespaceSelector matches a namespace where the attacker can create or update ServiceMonitor resources, the Collector pod has its service account token mounted, and the Collector can reach the attacker-controlled scrape target.
Workaround
This vulnerability can be mitigated by enabling the DenyFSAccessThroughSMs option, which causes the Target Allocator to drop ServiceMonitor and PodMonitor endpoints that reference arbitrary files on the file system.