CVE-2026-81192: OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS
OpenTelemetry.Resources.Host NuGet package, which provides OpenTelemetry resource detectors for host, is affected by an untrusted search path vulnerability on macOS. Prior to version 1.16.0-beta.2, the host.id resource attribute detector launches the sh and ioreg executables by bare name rather than by absolute path, so both are resolved through the PATH environment variable. A local attacker who is less privileged than the host application, and who can influence PATH or write to a directory that appears in PATH ahead of the system directories, can have an arbitrary binary executed in the application's security context, resulting in local code execution/privilege escalation. This vulnerability only affect macOS hosts - Linux and Windows hosts are unaffected. Version 1.16.0-beta.2 contains a patch. No known workarounds are available.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenTelemetry.Resources.Hostto a version that resolves this vulnerability.Fixed in 1.16.0-beta.2
Event History
Frequently Asked Questions
Which environments are exposed to this issue?
Only macOS hosts running a vulnerable version of the NuGet package are affected. Linux and Windows hosts are unaffected.
What does an attacker need to exploit it?
The attacker must have local access and be less privileged than the host application. They must be able to influence the application's PATH environment variable or place a malicious executable in a PATH directory that is searched before the system directories.
What is the impact if exploitation succeeds?
A malicious sh or ioreg executable can run in the security context of the host application. This can result in local code execution and privilege escalation when the application has greater privileges than the attacker.
How can I remediate the vulnerability?
Upgrade OpenTelemetry.Resources.Host to version 1.16.0-beta.2 or later, which contains the patch. No known workarounds are available if patching cannot be performed.