go.opentelemetry.io/otel/sdk
Affected
- introduced
1.15.0, fixed1.43.0(semver)
Fixed versions
1.43.0
Fix
- Fixed version
1.43.0go get go.opentelemetry.io/otel/[email protected]
Advisory
Also known as: CVE-2026-39883, GO-2026-5426
opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking
Summary
The fix for GHSA-9h8m-3fm2-qjrq (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.
Root Cause
sdk/resource/host_id.go line 42:
if result, err := r.execCommand("kenv", "-q", "smbios.system.uuid"); err == nil {
Compare with the fixed Darwin path at line 58:
result, err := r.execCommand("/usr/sbin/ioreg", "-rd1", "-c", "IOPlatformExpertDevice")
The execCommand helper at sdk/resource/host_id_exec.go uses exec.Command(name, arg...) which searches $PATH when the command name contains no path separator.
Affected platforms (per build tag in host_id_bsd.go:4): DragonFly BSD, FreeBSD, NetBSD, OpenBSD, Solaris.
The kenv path is reached when /etc/hostid does not exist (line 38-40), which is common on FreeBSD systems.
Attack
go.opentelemetry.io/otel/sdkkenv binary earlier in $PATHhostIDReaderBSD.read() calls exec.Command("kenv", ...) which resolves to the malicious binarySame attack vector and impact as CVE-2026-24051.
Suggested Fix
Use the absolute path:
if result, err := r.execCommand("/bin/kenv", "-q", "smbios.system.uuid"); err == nil {
On FreeBSD, kenv is located at /bin/kenv.
High Basis: The source's own band: HIGH
1.15.0, fixed 1.43.0 (semver)1.43.0
1.43.0go get go.opentelemetry.io/otel/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0