CVE-2026-47701: Github.com/open telemetry/opentelemetry operator OpenTelemetry Operator For Kubernetes's ServiceMonitor Vulnerability

HIGH
Advisory Identifier: GHSA-cxh2-4639-vmc5
CVSS 7.7
CWE-200
Published
Advisory Summary

CVE-2026-47701 is a HIGH (CVSS 7.7) opentelemetry operator for kubernetes's servicemonitor vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/open telemetry/opentelemetry operator libraries in the Go ecosystem. The issue involves opentelemetry operator for kubernetes's servicemonitor bearertokenfile reads arbitrary local file and sends contents as bearer auth. Remediation is available by upgrading affected packages to version 0.152.0.

CVE-2026-47701 at a Glance

CVE Identifier CVE-2026-47701
GHSA Identifier GHSA-cxh2-4639-vmc5
Severity HIGH
CVSS v3.1 Base Score 7.7
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/open telemetry/opentelemetry operator
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-47701

To remediate this vulnerability, upgrade all affected Github.com/open telemetry/opentelemetry operator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/open-telemetry/opentelemetry-operator fixed: 0.152.0
Upgrade github.com/open-telemetry/opentelemetry-operator to 0.152.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/open-telemetry/opentelemetry-operator

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-47701, inspect your project dependencies for Github.com/open telemetry/opentelemetry operator:

inspect dependencies for github.com/open-telemetry/opentelemetry-operator

Analyze the terminal output to locate any version of Github.com/open telemetry/opentelemetry operator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.152.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Github.com/open telemetry/opentelemetry operator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Affected Repository: github.com/open-telemetry/opentelemetry-operator Component: cmd/otel-allocator (TargetAllocator) Companion: Prometheus Operator API types (CRDs) ## Summary OpenTelemetry Operator's TargetAllocator watches `ServiceMonitor` resources via the Prometheus Operator CR watcher and converts each selected endpoint into a Prometheus scrape configuration entry. The endpoint field `bearerTokenFile` is preserved through the conversion as `HTTPClientConfig.Authorization.CredentialsFile`. The OpenTelemetry Collector, configured with the Prometheus receiver, then loads that scrape config and, at scrape time, reads the file from its own pod filesystem and sends the contents as `Authorization: Bearer ...` to the scrape endpoint. A tenant who can create or update a `ServiceMonitor` selected by TargetAllocator can set `bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token` and a scrape target the tenant controls. The Collector then ships its mounted service account JWT to that target on every scrape interval. The Prometheus Operator project addressed the same primitive via the `ArbitraryFSAccessThroughSMs.Deny` admission/runtime guard. ## Preconditions The OpenTelemetry Collector needs to be deployed with `targetAllocator.prometheusCR.enabled: true` and `serviceMonitorSelector` / `serviceMonitorNamespaceSelector` matching at least one namespace where the attacker can create or update `ServiceMonitor` (or paired with a TargetAllocator resource with the same respective settings). The Collector pod needs to have its service account token mounted. The Collector needs to be able to reach the scrape target chosen by the attacker. ## Impact Tenant `ServiceMonitor` write becomes equivalent to the OpenTelemetry Collector pod's service account against the Kubernetes API. Real impact depends on what the Collector service account is granted in a given deployment. Typical cluster monitoring setups grant pod, node, endpoint, namespace, and service list across the cluster, which is enough to enumerate and identify further targets. The same primitive can read any file the Collector pod has on disk including mounted certificates and other tokens. ## Fix https://github.com/open-telemetry/opentelemetry-operator/pull/5104 adds support to disable service and podmonitor endpoints that read arbitrary files. `DenyFSAccessThroughSMs` causes the Target Allocator to drop ServiceMonitor and PodMonitor endpoints that reference arbitrary files on the file system. When enabled, endpoints with bearerTokenFile, tlsConfig.caFile, tlsConfig.certFile, or tlsConfig.keyFile are dropped from the produced scrape configuration while the remaining endpoints are kept. This prevents tenants from stealing the Collector's service account token via ServiceMonitor bearerTokenFile references. This is the equivalent of `ArbitraryFSAccessThroughSMs.Deny` from the Prometheus Operator.

CVE-2026-47701 Affected Github.com/open telemetry/opentelemetry operator Versions

1 component(s)
Fixed Versions:
0.152.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/open-telemetry/opentelemetry-operator
Go
< 0.152.0
0.152.0

References

Frequently Asked Questions

What is CVE-2026-47701?
CVE-2026-47701 is a security vulnerability in Github.com/open telemetry/opentelemetry operator involving OpenTelemetry Operator for Kubernetes's ServiceMonitor bearerTokenFile reads arbitrary local file and sends contents as bearer auth under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/open telemetry/opentelemetry operator versions are affected?
Affected versions include releases prior to 0.152.0 across affected packages: github.com/open-telemetry/opentelemetry-operator.
What version fixes CVE-2026-47701?
Upgrading to 0.152.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/open-telemetry/opentelemetry-operator affected?
Yes, github.com/open-telemetry/opentelemetry-operator is affected in releases prior to 0.152.0. Upgrade your dependency to 0.152.0 or later.
What is the CVSS score of CVE-2026-47701?
CVE-2026-47701 has a CVSS v3.1 base score of 7.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-47701?
CVE-2026-47701 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for CVE-2026-47701?
Run the dependency tree command: 'inspect dependencies for github.com/open-telemetry/opentelemetry-operator'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cxh2-4639-vmc5",
  "modified" : "2026-06-10T17:24:01Z",
  "published" : "2026-06-10T17:24:01Z",
  "aliases" : [ "CVE-2026-47701" ],
  "summary" : "OpenTelemetry Operator for Kubernetes's ServiceMonitor bearerTokenFile reads arbitrary local file and sends contents as bearer auth",
  "details" : "## Affected\n\nRepository: github.com/open-telemetry/opentelemetry-operator\nComponent: cmd/otel-allocator (TargetAllocator)\nCompanion: Prometheus Operator API types (CRDs)\n\n## Summary\n\nOpenTelemetry Operator's TargetAllocator watches `ServiceMonitor` resources via the Prometheus Operator CR watcher and converts each selected endpoint into a Prometheus scrape configuration entry. The endpoint field `bearerTokenFile` is preserved through the conversion as `HTTPClientConfig.Authorization.CredentialsFile`. The OpenTelemetry Collector, configured with the Prometheus receiver, then loads that scrape config and, at scrape time, reads the file from its own pod filesystem and sends the contents as `Authorization: Bearer ...` to the scrape endpoint.\n\nA tenant who can create or update a `ServiceMonitor` selected by TargetAllocator can set `bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token` and a scrape target the tenant controls. The Collector then ships its mounted service account JWT to that target on every scrape interval.\n\nThe Prometheus Operator project addressed the same primitive via the `ArbitraryFSAccessThroughSMs.Deny` admission/runtime guard.\n\n## Preconditions\n\nThe OpenTelemetry Collector needs to be deployed with `targetAllocator.prometheusCR.enabled: true` and `serviceMonitorSelector` / `serviceMonitorNamespaceSelector` matching at least one namespace where the attacker can create or update `ServiceMonitor` (or paired with a TargetAllocator resource with the same respective settings). The Collector pod needs to have its service account token mounted. The Collector needs to be able to reach the scrape target chosen by the attacker.\n\n## Impact\n\nTenant `ServiceMonitor` write becomes equivalent to the OpenTelemetry Collector pod's service account against the Kubernetes API. Real impact depends on what the Collector service account is granted in a given deployment. Typical cluster monitoring setups grant pod, node, endpoint, namespace, and service list across the cluster, which is enough to enumerate and identify further targets. The same primitive can read any file the Collector pod has on disk including mounted certificates and other tokens.\n\n## Fix\n\nhttps://github.com/open-telemetry/opentelemetry-operator/pull/5104 adds support to disable service and podmonitor endpoints that read arbitrary files. \n`DenyFSAccessThroughSMs` causes the Target Allocator to drop ServiceMonitor and PodMonitor endpoints that reference arbitrary files on the file system. When enabled, endpoints with bearerTokenFile, tlsConfig.caFile, tlsConfig.certFile, or tlsConfig.keyFile are dropped from the produced scrape configuration while the remaining endpoints are kept. This prevents tenants from stealing the Collector's service account token via ServiceMonitor bearerTokenFile references. This is the equivalent of `ArbitraryFSAccessThroughSMs.Deny` from the Prometheus Operator.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/open-telemetry/opentelemetry-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.152.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-operator/security/advisories/GHSA-cxh2-4639-vmc5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-operator/pull/5104"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-telemetry/opentelemetry-operator"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-10T17:24:01Z",
    "nvd_published_at" : null
  }
}