Bug 2499680 (CVE-2026-47701) - CVE-2026-47701 opentelemetry-operator: OpenTelemetry Operator: ServiceMonitor bearerTokenFile reads arbitrary local file and sends contents as bearer auth
Summary: CVE-2026-47701 opentelemetry-operator: OpenTelemetry Operator: ServiceMonitor...
Keywords:
Status: NEW
Alias: CVE-2026-47701
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-13 14:36 UTC by OSIDB Bzimport
Modified: 2026-07-14 15:30 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-13 14:36:03 UTC
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. A tenant who can create or update a ServiceMonitor selected by TargetAllocator can set bearerTokenFile to /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. Preconditions: the Collector must be deployed with targetAllocator.prometheusCR.enabled: true and serviceMonitorSelector matching a namespace where the attacker can create ServiceMonitor. The Collector pod must have its service account token mounted and be able to reach the attacker's scrape target. Fixed in opentelemetry-operator 0.152.0 via PR #5104 which adds DenyFSAccessThroughSMs support.


Note You need to log in before you can comment on or make changes to this bug.