CVE-2026-41433: OpenTelemetry eBPF Path Traversal Flaw

CVE-2026-41433 Overview

CVE-2026-41433 is a path traversal vulnerability in OpenTelemetry eBPF Instrumentation (OBI) that allows local attackers to overwrite arbitrary host files through the Java agent injection mechanism. The flaw exists in versions 0.4.0 through 0.7.x, where the Java injector improperly trusts the TMPDIR environment variable from the target process and uses unsafe file creation semantics. This enables both filesystem boundary escape and symlink-based file clobbering attacks when Java injection is enabled and OBI runs with elevated privileges.

Critical Impact

Local attackers controlling a Java workload can achieve arbitrary file overwrite on the host system, potentially leading to privilege escalation, system compromise, or denial of service through corruption of critical system files.

Affected Products

• OpenTelemetry eBPF Instrumentation versions 0.4.0 to 0.7.x
• Environments with Java injection enabled
• Deployments running OBI with elevated (root) privileges

Discovery Timeline

• 2026-04-24 - CVE-2026-41433 published to NVD
• 2026-04-27 - Last updated in NVD database

Technical Details for CVE-2026-41433

Vulnerability Analysis

This vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), commonly known as path traversal. The flaw stems from the Java agent injector's trust relationship with user-controlled environment variables and lack of secure file handling practices.

When the OpenTelemetry eBPF Instrumentation tool performs Java agent injection, it creates temporary files in a directory specified by the target process's TMPDIR environment variable. Because the injector runs with elevated privileges but processes environment data from potentially untrusted workloads, an attacker can manipulate TMPDIR to point to arbitrary filesystem locations.

The absence of proper symlink resolution and boundary checking allows attackers to craft symlinks that redirect file write operations to sensitive system locations. This attack pattern can overwrite configuration files, system binaries, or other critical resources, leading to system instability or complete compromise.

Root Cause

The root cause is twofold: (1) the Java agent injector blindly trusts the TMPDIR environment variable from the target process without validation, and (2) the file creation routines do not implement secure practices such as O_NOFOLLOW flags or pre-creation symlink checks. This combination allows an attacker-controlled process to dictate where privileged file operations occur, breaking the expected security boundary between user workloads and the host system.

Attack Vector

The attack requires local access and the ability to control a Java workload being instrumented by OBI. An attacker performs the following steps:

1. Set the TMPDIR environment variable to a controlled directory
2. Create a symlink in the controlled directory pointing to a target file (e.g., /etc/passwd or a critical system binary)
3. Trigger Java agent injection, causing OBI to follow the symlink and overwrite the target file with injector-generated content

The attack exploits the Time-of-Check Time-of-Use (TOCTOU) race condition inherent in the unsafe file creation pattern, combined with the lack of filesystem boundary enforcement.

For detailed technical information on the vulnerability mechanism, refer to the GitHub Security Advisory GHSA-8gmg-3w2q-65f4.

Detection Methods for CVE-2026-41433

Indicators of Compromise

• Unexpected modifications to system files such as /etc/passwd, /etc/shadow, or system binaries
• Java workloads with suspicious TMPDIR environment variable settings pointing outside standard temporary directories
• Symlinks in temporary directories pointing to sensitive system paths
• OBI process file operations targeting unexpected filesystem locations

Detection Strategies

• Monitor file creation and modification events from OBI-related processes, particularly those targeting files outside /tmp or standard temp locations
• Implement file integrity monitoring (FIM) on critical system files to detect unauthorized modifications
• Audit Java workload environment variables for anomalous TMPDIR configurations
• Use SentinelOne's behavioral AI to detect privilege escalation patterns following file overwrites

Monitoring Recommendations

• Enable extended logging for OpenTelemetry eBPF Instrumentation to capture injection events
• Configure alerts for file system operations that cross security boundaries (e.g., writes to /etc, /usr, /var)
• Deploy auditd rules to track symlink creation in temporary directories used by instrumented workloads
• Monitor for process execution anomalies following unexpected file modifications

How to Mitigate CVE-2026-41433

Immediate Actions Required

• Upgrade OpenTelemetry eBPF Instrumentation to version 0.8.0 or later immediately
• If immediate upgrade is not possible, disable Java injection functionality until the patch can be applied
• Review all deployed OBI instances to identify those running with elevated privileges
• Audit systems for signs of prior exploitation, including unexpected file modifications

Patch Information

The vulnerability is fixed in OpenTelemetry eBPF Instrumentation version 0.8.0. The patch implements secure file creation semantics that prevent symlink following and validates the injection path to prevent filesystem boundary escape.

Download the patched version from the GitHub Release v0.8.0.

Workarounds

• Disable Java agent injection by removing or commenting out the Java injection configuration until the upgrade can be performed
• Run OBI with least-privilege principles where possible, avoiding root execution when not strictly required
• Implement mount namespace isolation for Java workloads to limit the impact of potential file overwrites
• Use container security policies to restrict TMPDIR modifications in instrumented workloads

# Disable Java injection in OBI configuration (example)
# Edit your OBI configuration file and set:
java_injection_enabled: false

# Or remove Java injection from the instrumentation targets list
# until upgrade to v0.8.0 is complete