CVE-2026-81192 — OpenTelemetry.Resources.H…
HIGHFix: open-telemetry/opentelemetry-dotnet-contrib#1631CVE-2026-81192 is a high-severity (CVSS 7) CWE-426 vulnerability in OpenTelemetry.Resources.Host. A fix is available for OpenTelemetry.Resources.Host — see the affected versions and patch details below.
OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-81192.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-81192 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
OpenTelemetry.Resources.HostReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
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.
The vulnerability was fixed by open-telemetry/opentelemetry-dotnet-contrib#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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | OpenTelemetry.Resources.Host | all versions | 1.16.0-beta.2dotnet add package OpenTelemetry.Resources.Host --version 1.16.0-beta.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OpenTelemetry.Resources.Host, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update OpenTelemetry.Resources.Host to 1.16.0-beta.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-81192 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-81192 in your dependencies?
Find it across NuGet, including transitive dependencies.