OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS
CVE-2026-81192GHSA-v8pv-4842-x354
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (opentelemetry.resources.host 1.16.0-beta.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
NuGet opentelemetry.resources.host
- Affected
- < 1.16.0-beta.2
- Fixed in
- 1.16.0-beta.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-v8pv-4842-x354 lists affected ranges: NuGet opentelemetry.resources.host >=0 <1.16.0-beta.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v8pv-4842-x354 lists affected ranges: NuGet opentelemetry.resources.host >=0 <1.16.0-beta.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-81192: 0.18% estimated exploitation activity in the next 30 days; percentile 7.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-v8pv-4842-x354
- Revision 1 · created ·
Published from osv record GHSA-v8pv-4842-x354
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-81192 Advisory: OpenTelemetry.Resources.Host vulnerable to arbitrary code execution via local PATH hijacking on macOS IDs: CVE-2026-81192, GHSA-v8pv-4842-x354 Record: https://patchnext.com/advisories/cve-2026-81192 (revision 2, source checked 26 Oct 2026, 17:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: opentelemetry.resources.host 1.16.0-beta.2. A vendor fix does not mean a deployment is fixed. ## Affected components - NuGet opentelemetry.resources.host: affected < 1.16.0-beta.2; fixed in 1.16.0-beta.2 ## Suggested inspection (read-only) - NuGet opentelemetry.resources.host: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on opentelemetry.resources.host. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-v8pv-4842-x354 (OSV record GHSA-v8pv-4842-x354 lists affected ranges: NuGet opentelemetry.resources.host >=0 <1.16.0-beta.2 (fixed)) - Verified: https://github.com/advisories/GHSA-v8pv-4842-x354 (GitHub-reviewed advisory GHSA-v8pv-4842-x354 lists affected ranges: NuGet opentelemetry.resources.host >=0 <1.16.0-beta.2) Commands are suggestions: review each one before running it.
Loading voting…