Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

opentelemetry-go · Vulnerability

CVSS 4.0 7.3 HIGHEUVD CVSS 4.0 7.3 CVSS 4.0 · [email protected] · Secondary 7.3 HIGHCVSS 3.1 · [email protected] · Primary 7.0 HIGHCVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 7.0 HIGHCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 8.8 HIGHCVSS_V4 Publisher rating HIGHFixed by go.opentelemetry.io/otel/sdk 1.43.0osv · severity unknownFixed by go.opentelemetry.io/otel/sdk 1.43.0KEV status unknown

cve-program · CVE-2026-39883

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-20630

Published

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.

Read the publisher's advisory

nvd · CVE-2026-39883

Published

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.

Read the publisher's advisory

osv · GHSA-hfvc-g4fc-pqhx

Published

## 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 1. Attacker has local access to a system running a Go application that imports `go.opentelemetry.io/otel/sdk` 2. Attacker places a malicious `kenv` binary earlier in `$PATH` 3. Application initializes OpenTelemetry resource detection at startup 4. `hostIDReaderBSD.read()` calls `exec.Command("kenv", ...)` which resolves to the malicious binary 5. Arbitrary code executes in the context of the application Same 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`.

Read the publisher's advisory

osv · GO-2026-5426

Published

Opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking in go.opentelemetry.io/otel/sdk

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-39883

Published

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.

Source published
8 Apr 2026 20:26:41 UTC
Source modified
9 Sep 2026 12:04:54 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 7.3 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

euvd · EUVD-2026-20630

Published

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 h…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Apr 8, 2026, 8:26:41 PM

dateUpdated: Sep 9, 2026, 12:04:54 PM

11 related source bulletins · separate from aliases

RHSA-2026:26257: Red Hat Security Advisory: Assisted Installer RHEL 8 components for Multicluster Engine for Kubernetes 2.8.8

CVE-2025-58058 · CVE-2026-39883

RHSA-2026:63140: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.19.2

CVE-2026-1965 · CVE-2026-3783 · CVE-2026-8286 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-15588 · CVE-2026-29181 · CVE-2026-39883 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58055

RHSA-2026:72395: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.20.1

CVE-2025-6170 · CVE-2026-1965 · CVE-2026-3783 · CVE-2026-5435 · CVE-2026-5928 · CVE-2026-6238 · CVE-2026-6653 · CVE-2026-8286 · CVE-2026-8458 · CVE-2026-8927 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-13757 · CVE-2026-14164 · CVE-2026-14456 · CVE-2026-14457 · CVE-2026-15588 · CVE-2026-16118 · CVE-2026-18798 · CVE-2026-29181 · CVE-2026-33186 · CVE-2026-39883 · CVE-2026-41989 · CVE-2026-46600 · CVE-2026-48864 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-54371 · CVE-2026-54874 · CVE-2026-56392 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58055 · CVE-2026-63072 · CVE-2026-63073 · CVE-2026-63074 · CVE-2026-63075 · CVE-2026-63076 · CVE-2026-63379 · CVE-2026-63381 · CVE-2026-63382 · CVE-2026-63383 · CVE-2026-63384 · CVE-2026-63385 · CVE-2026-63387 · CVE-2026-63388 · CVE-2026-81870 · CVE-2026-84445

RHSA-2026:72475: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.20.1

CVE-2025-6170 · CVE-2026-1965 · CVE-2026-3783 · CVE-2026-5435 · CVE-2026-5928 · CVE-2026-6238 · CVE-2026-6653 · CVE-2026-8286 · CVE-2026-8458 · CVE-2026-8927 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-13757 · CVE-2026-14164 · CVE-2026-14456 · CVE-2026-14457 · CVE-2026-15588 · CVE-2026-16118 · CVE-2026-18798 · CVE-2026-29181 · CVE-2026-33186 · CVE-2026-39883 · CVE-2026-41989 · CVE-2026-46600 · CVE-2026-48864 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-54371 · CVE-2026-54874 · CVE-2026-56392 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58055 · CVE-2026-63072 · CVE-2026-63073 · CVE-2026-63074 · CVE-2026-63075 · CVE-2026-63076 · CVE-2026-63379 · CVE-2026-63381 · CVE-2026-63382 · CVE-2026-63383 · CVE-2026-63384 · CVE-2026-63385 · CVE-2026-63387 · CVE-2026-63388 · CVE-2026-74860 · CVE-2026-81870 · CVE-2026-84445 · CVE-2026-86138 · CVE-2026-86140 · CVE-2026-86142 · CVE-2026-86143 · CVE-2026-86144

RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update

CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

RHSA-2026:54274: Red Hat Security Advisory: Red Hat OpenShift Workload Availability Operator v0.8.1 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33186 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39883 · CVE-2026-42499

openSUSE-SU-2026:11173-1: etcd-3.6.13-1.1 on GA media

CVE-2026-29181 · CVE-2026-39883

openSUSE-SU-2026:11494-1: clusterctl-1.14.0-1.1 on GA media

CVE-2026-39883

WID-SEC-W-2026-2929: Splunk Splunk Enterprise: Mehrere Schwachstellen

CVE-2026-76251 · CVE-2026-76252 · CVE-2026-76253 · CVE-2026-76254 · CVE-2026-76255 · CVE-2026-76256 · CVE-2026-76257 · CVE-2026-76258 · CVE-2026-76259 · CVE-2026-76260 · CVE-2026-76261 · CVE-2026-76262 · CVE-2026-76263 · CVE-2026-76309 · CVE-2026-76310 · CVE-2026-76311 · CVE-2026-76312 · CVE-2026-76313 · CVE-2026-76314 · CVE-2026-76315 · CVE-2026-76316 · CVE-2026-76317 · CVE-2026-76318 · CVE-2026-76319 · CVE-2026-76320 · CVE-2026-76321 · CVE-2026-76322 · CVE-2026-76323 · CVE-2026-76324 · CVE-2026-76325 · CVE-2026-76326 · CVE-2026-76327 · CVE-2026-76328 · CVE-2026-76329 · CVE-2026-76330 · CVE-2026-76331 · CVE-2026-76332 · CVE-2026-76333 · CVE-2026-76334 · CVE-2026-76335 · CVE-2026-76336 · CVE-2026-76337 · CVE-2026-76338 · CVE-2026-76339 · CVE-2026-76340 · CVE-2026-76341 · CVE-2026-76342 · CVE-2026-76343 · CVE-2026-76344 · CVE-2026-76345 · CVE-2026-76346 · CVE-2026-76347 · CVE-2026-76348 · CVE-2026-76349 · CVE-2026-76350 · CVE-2026-76351 · CVE-2026-76352 · CVE-2026-76353 · CVE-2026-76354 · CVE-2026-76355 · CVE-2024-35255 · CVE-2025-14017 · CVE-2025-14819 · CVE-2026-25679 · CVE-2026-27140 · CVE-2026-27143 · CVE-2026-27144 · CVE-2026-29181 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-33186 · CVE-2026-33810 · CVE-2026-34180 · CVE-2026-34986 · CVE-2026-39883 · CVE-2026-42766 · CVE-2026-45409 · CVE-2026-45447 · CVE-2026-6276 · CVE-2026-6429 · CVE-2026-6472 · CVE-2026-6473 · CVE-2026-6474 · CVE-2026-6475 · CVE-2026-6477 · CVE-2026-6478 · CVE-2026-6479 · CVE-2026-6637 · CVE-2026-6638 · CVE-2026-7168 · CVE-2026-7383 · CVE-2026-9076

RHSA-2026:54286: Red Hat Security Advisory: Red Hat OpenShift Workload Availability Operator v0.3.1 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33186 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39883 · CVE-2026-42499

RHSA-2026:26254: Red Hat Security Advisory: Assisted Installer RHEL 9 components for Multicluster Engine for Kubernetes 2.8.8

CVE-2025-58058 · CVE-2026-39883

Source published
Apr 8, 2026, 8:26:41 PM (timezone not stated)
Source modified
Sep 9, 2026, 12:04:54 PM (timezone not stated)
Saved here
15 Nov 2026 21:53:03 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 4.0 · 7.3 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

nvd · CVE-2026-39883

Published

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 h…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-426

Original publisher date fields

published: 2026-04-08T21:17:00.697

lastModified: 2026-09-09T13:19:48.837

1 source CPE criteria · context only
  • cpe:2.3:a:opentelemetry:opentelemetry:*:*:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
8 Apr 2026 21:17:00 UTC
Source modified
9 Sep 2026 13:19:48 UTC
Saved here
25 Oct 2026 09:17:24 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · [email protected] · Secondary · 7.3 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CVSS 3.1 · [email protected] · Primary · 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary · 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

osv · GHSA-hfvc-g4fc-pqhx

Published

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 1. Attacker has local access to a system running a Go application that imports `go.opentelemetry.io/otel/sdk` 2. Attacker places a malicious `kenv` binary earlier in `$PATH` 3. Application initializes OpenTelemetry resource detection at startup 4. `hostIDReaderBSD.read()` calls `exec.Command("kenv", ...)` which resolves to the malicious binary 5. Arbitrary code executes in the context of the application Same 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`.

Source published
8 Apr 2026 19:22:12 UTC
Source modified
10 Sep 2026 03:51:01 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V4 · 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

Publisher rating · HIGH

osv · GO-2026-5426

Published

Opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking in go.opentelemetry.io/otel/sdk

Opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking in go.opentelemetry.io/otel/sdk

Source published
24 Jul 2026 18:35:55 UTC
Source modified
30 Jul 2026 15:59:51 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current