CVE-2026-24051 Details
Description
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.
A path hijacking vulnerability allowing arbitrary code execution has been identified in the OpenTelemetry Go SDK, specifically in versions 1.20.0 prior to 1.39.0. This issue arises on macOS systems, where the resource detection code executes the 'ioreg' command using a search path. An attacker who can locally modify the PATH environment variable could exploit this vulnerability to execute arbitrary code within the application's context.
Users can upgrade to OpenTelemetry Go SDK version 1.40.0 or later to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-426 | Untrusted Search Path | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| opentelemetry opentelemetry | >= 1.21.0, < 1.40.0 |
CPE
Remediation
| |
| apple macos | All versions |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | Modified Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 15, 2026 | Reanalysis | [email protected] |
| Feb 27, 2026 | Initial Analysis | [email protected] |
| Feb 2, 2026 | New CVE Received | [email protected] |