# CVE-2026-41433: OpenTelemetry eBPF Instrumentation: Privileged Java agent injection allows arbitrary host file overwrite via untrusted TMPDIR

> A local attacker can overwrite arbitrary host files via unsafe Java agent injection when OpenTelemetry eBPF instrumentation runs with elevated privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 25 Apr 2026
- **Also known as:** GHSA-8gmg-3w2q-65f4, GO-2026-5253

## What is CVE-2026-41433?

CVE-2026-41433 is a high-severity path traversal vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-41433?

3 open source packages ship an affected version, including go.opentelemetry.io/obi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `go.opentelemetry.io/obi` | Go | From 0.4.0 | 0.8.0 |
| `go.opentelemetry.io/obi` | Go | From 0.4.0 | 0.8.0 |
| `go.opentelemetry.io/obi` | Go | From 0.4.0 | 0.8.0 |

Products: Opentelemetry Opentelemetry Ebpf Instrumentation.

## How do I fix CVE-2026-41433?

Upgrade go.opentelemetry.io/obi to 0.8.0 or later.

## Is CVE-2026-41433 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41433 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41433 and fix it if it is affected.

What it is: CVE-2026-41433 is a high-severity path traversal vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41433 exists.

Affected packages and fixed versions:
- go.opentelemetry.io/obi (Go): affected from 0.4.0; fixed in 0.8.0
- go.opentelemetry.io/obi (Go): affected from 0.4.0; fixed in 0.8.0
- go.opentelemetry.io/obi (Go): affected from 0.4.0; fixed in 0.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41433/ (Markdown: https://insights.sbomify.com/CVE-2026-41433/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41433
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41433
- OSV: https://osv.dev/vulnerability/CVE-2026-41433

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41433/
Summaries are generated and may contain mistakes; the official description above is the record.