CVE-2026-81192 json
OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS
published 2mo ago modified last mo. also EUVD-2026-74187 , GHSA-v8pv-4842-x354
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
`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.
Patch / fix
- nuget OpenTelemetry.Resources.Host 1.16.0-beta.2
- opentelemetry opentelemetry.exporter.onecollector 1.16.0-beta.2
- opentelemetry opentelemetry.opamp.client 1.16.0-beta.2
- opentelemetry opentelemetry.resources.azure 1.16.0-beta.2
Is CVE-2026-81192 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | OpenTelemetry.Resources.Host | <1.16.0-beta.2 |
1.16.0-beta.2 |
Affected products
- open-telemetry opentelemetry-dotnet-contrib
Classification
- Weakness
-
- CWE-426 Untrusted Search Path
References
-
github.com
/open-telemetry/opentelemetry-dotnet-contrib/pull/1631
web
-
github.com
/open-telemetry/opentelemetry-dotnet-contrib/pull/4760
web
-
github.com
/open-telemetry/opentelemetry-dotnet-contrib/security/advisories/GHSA-v8pv-4842-x354
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-81192
advisory
-
github.com
/open-telemetry/opentelemetry-dotnet-contrib
package
Sources
- CVE List CVE-2026-81192
- GitHub Advisory GHSA-v8pv-4842-x354
- NVD CVE-2026-81192
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.