Skip to content
Fencer Intel
high 7.0

CVE-2026-24051 json

OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking

published 9mo ago modified 21d ago also EUVD-2026-5303 , GHSA-9h8m-3fm2-qjrq , GO-2026-4394

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

OpenTelemetry-Go is the Go implementation of OpenTelemetry. The OpenTelemetry Go SDK in version v1.20.0-1.39.0 is vulnerable to Path Hijacking (Untrusted Search Paths) on macOS/Darwin systems. The resource detection code in sdk/resource/host_id.go executes the ioreg system command using a search path. An attacker with the ability to locally modify the PATH environment variable can achieve Arbitrary Code Execution (ACE) within the context of the application. A fix was released with v1.40.0.

Patch / fix

  • go go.opentelemetry.io/otel/sdk 1.40.0
  • linuxfoundation opentelemetry-go 1.40.0
  • opentelemetry opentelemetry 1.40.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1

suse advisories SUSE-SU-2026:0757-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • copacetic openSUSE Tumbleweed 0.14.0-1.1
  • teleport openSUSE Tumbleweed 17.7.23-1.1
  • kyverno openSUSE Tumbleweed 1.17.2-1.1
  • openbao openSUSE Tumbleweed 2.5.1-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:10716-1openSUSE-SU-2026:10684-1openSUSE-SU-2026:10613-1openSUSE-SU-2026:10396-1

Is CVE-2026-24051 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-24051 updated cvss 7.0

opentelemetry-go: OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking

  • Red Hat Fence Agents Remediation Operator redhat-user-workloads/rhwa-tenant/fence-agents-remediation/far-operator-0-8 Red Hat Multicluster Engine for Kubernetes multicluster-engine/mce-capi-webhook-config-rhel9
    affected: workaround, no fix available
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-kuberay-operator-controller-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Storage-Based Remediation redhat-user-workloads/rhwa-tenant/storage-based-remediation/sbr-operator-0-3
    affected: workaround, no fix available
  • Red Hat Multicluster Engine for Kubernetes multicluster-engine/cluster-api-provider-aws-rhel9
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
9mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go go.opentelemetry.io/otel/sdk
>=1.21.0, <1.40.0
1.40.0

Affected products

  • open-telemetry opentelemetry-go

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.