Loading...
Skip to main content

CVE-2026-81192 — Vulnerability in OpenTelemetry.Resources.Host —...

HIGH

OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS

Published September 16, 2026Updated September 16, 2026Source: osv

Summary

### Summary The `OpenTelemetry.Resources.Host` NuGet package is affected by an untrusted search path vulnerability on macOS. 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. ### Details The implementation of the host detector macOS has always invoked `ioreg` and `sh` via their bare names since it was implemented by [open-telemetry/opentelemetry-dotnet-contrib#1631](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/1631). The vulnerability was fixed by [open-telemetry/opentelemetry-dotnet-contrib#4760](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4760) which executes `ioreg` directly using its absolute path. ### Impact Applications running on **macOS** that use the `OpenTelemetry.Resources.Host` detector when an attacker who is *less privileged* than the application process can influence `PATH` or write to a `PATH` directory that precedes the system directories (e.g. a higher-privileged service with a user-writable directory in its search path, or a process inheriting an attacker-influenced environment). The attacker gains code execution in the application's security context through an attacker-controlled `ioreg` executable. ### Mitigation This vulnerability only affect macOS hosts - Linux and Windows hosts are unaffected. ### Workarounds None known. ### References - [GHSA-9h8m-3fm2-qjrq](https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-9h8m-3fm2-qjrq) - [open-telemetry/opentelemetry-dotnet-contrib#4760](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4760) - [CWE-426](https://cwe.mitre.org/data/definitions/426.html)

Advisory Timeline

  • First published September 16, 2026 (26 days ago).
  • Last revised September 16, 2026 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update OpenTelemetry.Resources.Host to 1.16.0-beta.2 or later
dotnet add package OpenTelemetry.Resources.Host --version 1.16.0-beta.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: nuget (1).

PackageEcosystemAffectedFixed In
OpenTelemetry.Resources.Host
nuget
All versions1.16.0-beta.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.0 score means for each attack dimension.

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-81192?
OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.0/10).
How do I check if my project is affected by CVE-2026-81192?
CVE-2026-81192 affects OpenTelemetry.Resources.Host. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-81192 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.0

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-v8pv-4842-x354

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies