CVE-2026-39883: OpenTelemetry-Go has an incomplete fix for CVE-2026-24051: BSD kenv command not using absolute path enables PATH hijacking
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.15.0 to 1.42.0, the fix for CVE-2026-24051 changed the Darwin ioreg command to use an absolute path but left the BSD kenv command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms. This vulnerability is fixed in 1.43.0.
Security readout for executives and security teams
Plain-English summary
A locally authenticated attacker may trick affected OpenTelemetry-Go software on BSD or Solaris into running a malicious program named kenv. Successful abuse could cross a security boundary and compromise confidentiality, integrity, and availability. Versions 1.15.0 through 1.42.0 are affected; version 1.43.0 fixes the issue.
Executive priority
Treat as a high-priority patching item for BSD and Solaris environments, especially multi-user systems or privileged services. Inventory first because OpenTelemetry-Go may be included transitively. Accelerate remediation where untrusted local users can influence PATH; other platforms are not identified as affected by this specific kenv issue.
Technical view
The incomplete CVE-2026-24051 fix gave Darwin's ioreg command an absolute path but left BSD's kenv invocation as a bare command name. If an attacker can influence PATH resolution, affected software may execute an attacker-controlled kenv binary. The CVSS 3.1 score is 8.8, with local access and low privileges required.
Likely exposure
Exposure is limited to deployments containing OpenTelemetry-Go versions 1.15.0 through 1.42.0 on BSD or Solaris where the vulnerable kenv path executes. Risk depends on whether a low-privileged local user can influence the process PATH or place a matching executable in a searched directory.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as KEV. Exploitation requires local access, low privileges, and control over command resolution through PATH. No user interaction is required; successful execution may affect resources beyond the vulnerable component's original security scope.
Researcher notes
This is CWE-426, untrusted search path, and an incomplete remediation of CVE-2026-24051. Analysis should confirm the affected kenv invocation is reachable in the deployed build and operating environment. The bundle provides no proof of public exploitation or details establishing exposure on platforms beyond BSD and Solaris.
Mitigation direction
Upgrade OpenTelemetry-Go to version 1.43.0 or later.
Identify direct and transitive dependencies using affected versions.
Prioritize exposed BSD and Solaris workloads with locally accessible accounts.
Apply applicable Red Hat security errata for packaged downstream products.
Until upgraded, restrict PATH modification and writable PATH directories.
Validation and detection
Confirm the resolved OpenTelemetry-Go version is 1.43.0 or later.
Identify affected workloads running on BSD or Solaris.
Review service PATH values and permissions on every searched directory.
Verify unprivileged users cannot introduce executables into searched directories.
Recheck downstream package status against applicable vendor advisories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-426: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
3CVSS vectors
5Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
3 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-426 · source CWE mapping
Untrusted Search Path
Untrusted Search Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.