LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A security hardening fix in OpenTelemetry-Go missed one platform-specific command lookup. On BSD and Solaris systems, affected applications may run a command found through PATH instead of a fixed system path. A local low-privileged attacker could abuse that condition to run unintended code in the application’s context.

Executive priority

Treat this as high priority where OpenTelemetry-Go is deployed on BSD or Solaris. It is a local-privilege prerequisite issue, not confirmed internet-wide exploitation, but the potential impact is high and the upstream fix is identified.

Technical view

OpenTelemetry-Go versions 1.15.0 through 1.42.0 contain CWE-426 untrusted search path behavior for the BSD kenv command. The earlier CVE-2026-24051 fix used an absolute path for Darwin ioreg but left BSD/Solaris kenv as a bare command name. Fixed upstream version is 1.43.0.

Likely exposure

Exposure is most likely in Go applications or downstream packages using OpenTelemetry-Go >=1.15.0 and <1.43.0 on BSD or Solaris. The provided sources do not establish Linux, Windows, or Darwin exposure for this CVE. Red Hat package impact should be checked through its listed advisories and VEX data.

Exploitation context

The CVSS vector describes local access, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The source bundle marks KEV as false, and no cited source here supports active exploitation in the wild.

Researcher notes

Focus triage on CWE-426 behavior around the BSD kenv invocation and the incomplete CVE-2026-24051 fix. Avoid assuming exploitability outside BSD/Solaris from these sources. Downstream package status may differ from upstream and should be validated through vendor advisories.

Mitigation direction

  • Upgrade OpenTelemetry-Go to version 1.43.0 or later.
  • Inventory applications and dependencies for opentelemetry-go versions 1.15.0 through 1.42.0.
  • Prioritize BSD and Solaris deployments using affected versions.
  • Review Red Hat errata for downstream package-specific remediation.
  • If upgrade timing is constrained, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Confirm the exact opentelemetry-go version in source and built artifacts.
  • Check whether affected services run on BSD or Solaris platforms.
  • Review dependency lockfiles, SBOMs, and container/package metadata.
  • Verify upgraded builds include opentelemetry-go 1.43.0 or later.
  • Track Red Hat VEX and advisories for environment-specific status.
Prepared
Confidence
high
Sources
9

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-39883 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
8Source 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26redhat-SADP
7.3CVSS 4.0HighCVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_M
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9CISA-ADP

Vulnerability scoring details

Base CVSS 4.0 score

7.3High
CVSS 4.0 vector shape for CVE-2026-39883Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgithub.com/open-telemetry/opentelemetry-go: OpenTelemetry-Go: Arbitrary code execution via PATH hijacking on BSD/Solaris
other:Red Hat severity ratingcvssV3_1
  • 2026-04-08T21:01:31.690Z: Reported to Red Hat.
  • 2026-04-08T20:26:41.731Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
open-telemetryopentelemetry-go>= 1.15.0, < 1.43.0Listed
Weakness

CWE details

CWE-426

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.

Open CWE intelligenceSame-CWE CVEs