# CVE-2026-39883: OpenTelemetry OpenTelemetry-Go untrusted search path in host ID detection

Source: https://junglewise.ai/threats/cve-2026-39883-opentelemetry-opentelemetry-go-untrusted-search-path-in-host-id  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-08. Updated: 2026-06-30  
License: CC BY 4.0 with a link back

CVE-2026-39883 · Severity: high · CVSS 7 · Published 2026-04-08

OpenTelemetry-Go is a software library used by developers to monitor and trace the performance of Go-based applications. A security flaw in how the library identifies the host system on BSD and Solaris platforms allows a local attacker to trick the application into running malicious code. This could lead to a full system compromise or unauthorized access to sensitive application data.

Technologies: [go.opentelemetry.io/otel/sdk (Go)](https://junglewise.ai/threats/technologies/go-opentelemetry-io-otel-sdk), [Opentelemetry Go SDK](https://junglewise.ai/threats/technologies/go-sdk), [Opentelemetry](https://junglewise.ai/threats/technologies/opentelemetry). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Opentelemetry](https://junglewise.ai/threats/vendors/opentelemetry).

## Quick answers

**Is CVE-2026-39883 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-39883 being exploited in the wild.

**How severe is CVE-2026-39883?** High severity, with a CVSS score of 7, published 8 April 2026.

**Which products and versions are affected?** go.opentelemetry.io/otel/sdk (Go) SEMVER:introduced=1.15.0,fixed=1.43.0; Opentelemetry Go SDK >= 1.15.0, < 1.43.0.

**Is there a fix for CVE-2026-39883?** Yes. go.opentelemetry.io/otel/sdk (Go): upgrade to 1.43.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-39883 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-39883?** Check whether you run go.opentelemetry.io/otel/sdk (Go), Opentelemetry Go SDK or Opentelemetry at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- go.opentelemetry.io/otel/sdk (Go): upgrade to 1.43.0 or later

  ```sh
  go get go.opentelemetry.io/otel/sdk@v1.43.0
  ```


## Technical details

OpenTelemetry-Go is vulnerable to an untrusted search path (CWE-426) in its host resource detection component. While a previous fix (CVE-2026-24051) addressed this for Darwin by using absolute paths for the 'ioreg' command, the 'kenv' command used on BSD and Solaris platforms remained unpatched. The library uses 'exec.Command' with a bare name, which causes the Go runtime to search the system PATH. A local attacker with low privileges can place a malicious 'kenv' binary in a directory earlier in the PATH, leading to arbitrary code execution when the application initializes resource detection. This affects DragonFly BSD, FreeBSD, NetBSD, OpenBSD, and Solaris. The issue is resolved in version 1.43.0 by using the absolute path '/bin/kenv'.

## Affected products

- OpenTelemetry opentelemetry-go >= 1.15.0, < 1.43.0
- Red Hat multicluster engine for Kubernetes 2.8 2.8.8

## Identifiers

- CVE-2026-39883
- GHSA-hfvc-g4fc-pqhx
- GO-2026-5426

## Timeline

- 2026-04-03: patched: Version 1.43.0 released
- 2026-04-08: disclosed: GitHub Security Advisory published
- 2026-04-08: advisory: NVD published CVE-2026-39883
- 2026-06-16: advisory: Red Hat security advisory RHSA-2026:26254 published

## References

- [http://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.43.0](http://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.43.0)
- [https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hfvc-g4fc-pqhx](https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hfvc-g4fc-pqhx)
- [https://access.redhat.com/errata/RHSA-2026:26254](https://access.redhat.com/errata/RHSA-2026:26254)
- [https://access.redhat.com/errata/RHSA-2026:26257](https://access.redhat.com/errata/RHSA-2026:26257)
- [https://access.redhat.com/security/cve/CVE-2026-39883](https://access.redhat.com/security/cve/CVE-2026-39883)
- [https://bugzilla.redhat.com/show_bug.cgi?id=2456718](https://bugzilla.redhat.com/show_bug.cgi?id=2456718)
- [https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-39883.json](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-39883.json)

## Related threats

- [OpenTelemetry-Go attribute truncation bypass with Unicode replacement character](https://junglewise.ai/threats/cve-2026-81869-opentelemetry-go-attribute-truncation-bypass-with-unicode)
- [OpenTelemetry-Go endpoint URL logging in TracerProvider diagnostics](https://junglewise.ai/threats/cve-2026-81870-opentelemetry-go-endpoint-url-logging-in-tracerprovider)
- [OpenTelemetry .NET has potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path](https://junglewise.ai/threats/cve-2026-41078-opentelemetry-net-has-potential-memory-exhaustion-via-unbounded)
- [OpenTelemetry dotnet: Excessive memory allocation when parsing OpenTelemetry propagation headers](https://junglewise.ai/threats/cve-2026-40894-opentelemetry-dotnet-excessive-memory-allocation-when-parsing)
- [OpenTelemetry dotnet: Unbounded `grpc-status-details-bin` parsing in OTLP/gRPC retry handling](https://junglewise.ai/threats/cve-2026-40891-opentelemetry-dotnet-unbounded-grpc-status-details-bin-parsing-in)