CVE-2026-47701 open-telemetry CVE debrief

Who should care

Kubernetes administrators and users with access to the OpenTelemetry Operator should assess their exposure and prioritize upgrading to version 0.152.0. Defenders should care about this vulnerability as it allows tenants to potentially disclose sensitive information, including the Collector's service-account JWT or other mounted files, by manipulating ServiceMonitor endpoints.

Why it matters

Defenders should care about this vulnerability as it allows tenants to potentially disclose sensitive information, including the Collector's service-account JWT or other mounted files, by manipulating ServiceMonitor endpoints. This issue requires verification of Collector configurations and ServiceMonitor endpoints, and upgrading to version 0.152.0 or later.

• Potential disclosure of Collector's service-account JWT or other mounted files
• Unauthorized access to sensitive information
• Possible impact on Kubernetes API

Technical summary

The OpenTelemetry Operator's TargetAllocator instances with targetAllocator.prometheusCR.enabled set to true preserve a selected ServiceMonitor endpoint's bearerTokenFile value as HTTPClientConfig.Authorization.CredentialsFile. This allows tenants to potentially disclose the Collector's service-account JWT or other mounted files. 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.

Defensive priority

Defenders should prioritize upgrading to version 0.152.0 and verify their Collector configurations.

Recommended defensive actions

• Upgrade to OpenTelemetry Operator version 0.152.0 or later
• Verify Collector configurations and ServiceMonitor endpoints
• Review and restrict access to sensitive files in the Collector pod
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability allows tenants to point bearerTokenFile at sensitive files in the Collector pod, including /var/run/secrets/kubernetes.io/serviceaccount/token. Exploitation requires the Collector service-account token or another sensitive file to be mounted and the Collector to reach the chosen target.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.