OpenTelemetry eBPF Instrumentation EUVD-2026-25620

Requires three specific conditions: (1) Java agent injection feature explicitly enabled in OpenTelemetry eBPF Instrumentation configuration (non-default feature flag), (2) OBI process running with elevated privileges such as root or CAP_DAC_OVERRIDE and CAP_SYS_PTRACE capabilities to inject into target processes and write arbitrary filesystem locations, and (3) attacker control over a Java workload on the same host, including ability to set environment variables like TMPDIR for the target process. Exploitation is limited to environments where the agent is deployed with privilege elevation (common in Kubernetes DaemonSet patterns for observability agents) and where Java auto-instrumentation is actively used. Does NOT affect deployments using only eBPF-based passive observation without agent injection, installations running OBI without elevated privileges (though this breaks Java injection functionality), or environments not processing Java workloads.

Real-world risk is HIGH for environments meeting specific deployment conditions but lower than raw CVSS 8.4 suggests for most deployments. Attack requires three conditions: (1) Java injection feature explicitly enabled, (2) OBI running with elevated privileges (root or specific capabilities), and (3) attacker control over a Java workload on the host. The local attack vector (AV:L) and low privilege requirement (PR:L) mean remote exploitation is not possible, limiting exposure compared to network-based vulnerabilities. However, the scope change to host (S:C) represents significant container escape risk in multi-tenant Kubernetes environments where malicious workloads could compromise the underlying node. No EPSS data available, and absence from CISA KEV suggests no widespread exploitation detected. The attack complexity is low (AC:L) once conditions are met, as demonstrated by the technical details showing straightforward TMPDIR manipulation. Primary risk population: DevOps teams running OpenTelemetry auto-instrumentation in production Kubernetes with shared nodes hosting untrusted workloads. Lower risk for: single-tenant environments, deployments not using Java injection, or installations running OBI without elevated privileges (though this may break intended functionality).

An attacker with access to deploy a malicious Java application in a Kubernetes cluster sets the TMPDIR environment variable to '/host-root/etc' pointing through a container volume mount or sets it to a symlink targeting '/etc/cron.d'. When the privileged OpenTelemetry eBPF agent injects instrumentation into this Java process, it trusts the attacker-controlled TMPDIR and writes temporary files through the symlink, overwriting '/etc/cron.d/malicious-job' on the host filesystem. The attacker achieves container escape with arbitrary file write capability, enabling privilege escalation to full node compromise by scheduling malicious cron jobs or overwriting SSH authorized_keys files.