Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24051: CWE-426: Untrusted Search Path in open-telemetry opentelemetry-go

0
High
VulnerabilityCVE-2026-24051cvecve-2026-24051cwe-426
Published: Mon Feb 02 2026 (02/02/2026, 19:49:10 UTC)
Source: CVE Database V5
Vendor/Project: open-telemetry
Product: opentelemetry-go

Description

CVE-2026-24051 is a high-severity vulnerability affecting the OpenTelemetry-Go SDK versions 1. 21. 0 up to but not including 1. 40. 0 on macOS/Darwin systems. The vulnerability arises from an untrusted search path (CWE-426) in the resource detection code that executes the 'ioreg' system command without specifying an absolute path. An attacker with local access who can modify the PATH environment variable can hijack this command execution to run arbitrary code within the application's context. This flaw allows for arbitrary code execution without user interaction but requires local privileges and a high attack complexity. No known exploits are currently reported in the wild. The issue was fixed in version 1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/10/2026, 11:14:04 UTC

Technical Analysis

CVE-2026-24051 is a vulnerability in the OpenTelemetry-Go SDK, specifically affecting versions from 1.21.0 up to 1.39.0 on macOS/Darwin platforms. The root cause is an untrusted search path (CWE-426) in the resource detection component located in sdk/resource/host_id.go, which executes the 'ioreg' system command without specifying its absolute path. This allows an attacker with local access and the ability to modify the PATH environment variable to influence which executable is run when the application calls 'ioreg'. By placing a malicious executable earlier in the PATH, the attacker can achieve arbitrary code execution within the context of the vulnerable application. The vulnerability requires local privileges to modify environment variables and has a high attack complexity due to the need for local access and environment manipulation. The CVSS v3.1 score is 7.0, reflecting high impact on confidentiality, integrity, and availability, but limited by the requirement for local privileges and no user interaction. No public exploits have been reported, but the risk remains significant for environments where local user controls are weak or where multiple users share systems. The issue was addressed in OpenTelemetry-Go version 1.40.0 by presumably specifying absolute paths or otherwise securing command execution.

Potential Impact

For European organizations, the impact of CVE-2026-24051 is primarily on systems running macOS with vulnerable versions of OpenTelemetry-Go SDK. Organizations using OpenTelemetry for telemetry and observability in Go applications on macOS could face arbitrary code execution risks if an attacker gains local access and can manipulate environment variables. This could lead to unauthorized data access, system compromise, or disruption of telemetry services, potentially affecting monitoring and incident response capabilities. The vulnerability could be exploited in environments with shared workstations, developer machines, or CI/CD systems where local user controls are insufficient. Confidentiality, integrity, and availability of telemetry data and the host system are at risk. Given the high CVSS score, the threat is significant but constrained by the need for local access and environment manipulation. European organizations with macOS-based development or monitoring infrastructure should prioritize patching to avoid lateral movement or privilege escalation scenarios.

Mitigation Recommendations

1. Upgrade all OpenTelemetry-Go SDK instances to version 1.40.0 or later, which contains the fix for this vulnerability. 2. Enforce strict local user permissions to prevent unauthorized modification of the PATH environment variable, especially on macOS systems running vulnerable versions. 3. Implement application whitelisting or integrity monitoring to detect unauthorized changes to executables or environment configurations. 4. Use containerization or sandboxing to isolate telemetry applications and limit the impact of potential local exploits. 5. Audit and restrict local access to systems running OpenTelemetry-Go to trusted users only. 6. Monitor logs and system behavior for unusual command executions or environment variable changes. 7. Educate developers and system administrators about the risks of untrusted search paths and secure coding practices related to command execution.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-20T22:30:11.778Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69813005f9fa50a62f63a3db

Added to database: 2/2/2026, 11:15:17 PM

Last enriched: 2/10/2026, 11:14:04 AM

Last updated: 3/24/2026, 12:18:08 AM

Views: 236

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses