What is the CVSS score of CVE-2026-41433?

CVE-2026-41433 has a CVSS 3.1 base score of 8.4 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of OpenTelemetry eBPF Instrumentation are affected by CVE-2026-41433?

OpenTelemetry eBPF Instrumentation versions 0.4.0-0.7.x contain a local privilege escalation vulnerability allowing attackers with Java workload access to overwrite arbitrary host files when the…. A patch is available.

How to fix or mitigate CVE-2026-41433?

Within 24 hours: Identify all deployments of OpenTelemetry eBPF Instrumentation versions 0.4.0-0.7.x in your environment using asset inventory or container scanning tools. Within 7 days: Upgrade all affected instances to version 0.8.0 or later per vendor advisory; if immediate patching is impossible, disable Java injection or restrict the agent to run without elevated privileges. Within 30 days: Validate patch deployment across all environments, audit Java workload isolation controls, and implement TMPDIR environment variable restrictions to prevent symlink-based attacks.

OpenTelemetry eBPF Instrumentation CVE-2026-41433

EUVD-2026-25620 HIGH

Path Traversal (CWE-22)

2026-04-24 GitHub_M

GHSA-8gmg-3w2q-65f4

Java Path Traversal

8.4

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.4 HIGH

AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

None

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Apr 27, 2026 - 18:57 nvd

Patch available

Apr 24, 2026 - 21:02 EUVD

Re-analysis Queued

Apr 24, 2026 - 20:22 vuln.today

cvss_changed

Analysis Generated

Apr 24, 2026 - 20:16 vuln.today

EUVD ID Assigned

Apr 24, 2026 - 19:45 euvd

EUVD-2026-25620

Analysis Generated

Apr 24, 2026 - 19:45 vuln.today

CVE Published

Apr 24, 2026 - 19:26 nvd

HIGH 8.4

DescriptionGitHub Advisory

OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. From 0.4.0 to before 0.8.0, a flaw in the Java agent injection path allows a local attacker controlling a Java workload to overwrite arbitrary host files when Java injection is enabled and OBI is running with elevated privileges. The injector trusted TMPDIR from the target process and used unsafe file creation semantics, enabling both filesystem boundary escape and symlink-based file clobbering. This vulnerability is fixed in 0.8.0.

AnalysisAI

OpenTelemetry eBPF Instrumentation versions 0.4.0 through 0.7.x allow local attackers controlling a Java workload to overwrite arbitrary host files via path traversal when Java injection is enabled and the agent runs with elevated privileges. The vulnerability exploits unsafe file creation in the Java agent injection path, where the injector trusts the target process's TMPDIR environment variable and lacks boundary checks, enabling symlink-based file clobbering and filesystem escape. Vendor-released patch available in version 0.8.0. No public exploit identified at time of analysis, but CVSS 8.4 reflects high integrity and availability impact with scope change from container to host.

Technical ContextAI

OpenTelemetry eBPF Instrumentation uses eBPF (extended Berkeley Packet Filter) to provide low-overhead instrumentation for applications. The Java agent injection mechanism dynamically injects OpenTelemetry instrumentation into running Java processes. The vulnerability stems from CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal). The injector reads TMPDIR from the untrusted target process environment and uses it to create temporary files without validating that the path stays within safe boundaries. When OBI runs with elevated privileges (common in containerized environments where the agent needs CAP_SYS_PTRACE or root to inject into processes), an attacker controlling a Java workload can set TMPDIR to escape chroot/container boundaries or point to a symlink that redirects file writes to critical host paths. The CVSS scope change (S:C) indicates container-to-host escape potential, consistent with typical Kubernetes/Docker deployments where instrumentation agents run privileged.

RemediationAI

Upgrade to OpenTelemetry eBPF Instrumentation version 0.8.0 or later, which implements input validation for TMPDIR and safe file creation semantics to prevent path traversal (vendor-released patch confirmed at https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.8.0). For environments unable to upgrade immediately, disable Java agent injection if not operationally required, accepting loss of automatic Java instrumentation until patching is possible. Alternatively, run OBI with minimal privileges using capability-based restrictions (drop all capabilities except CAP_SYS_PTRACE) rather than full root, though this may not fully mitigate the vulnerability if the injector still has write access to sensitive paths. Deploy container security policies (AppArmor, SELinux) restricting file write operations to specific directories, noting this adds operational complexity and may interfere with legitimate instrumentation functionality. Isolate untrusted workloads to dedicated nodes where OBI is not deployed, accepting reduced observability coverage for high-risk applications. Review audit logs for suspicious TMPDIR values or unexpected file creation patterns in /proc/[pid]/environ of injected Java processes.