How severe is GHSA-hfvc-g4fc-pqhx?

No CVSS score has been assigned to GHSA-hfvc-g4fc-pqhx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hfvc-g4fc-pqhx?

GHSA-hfvc-g4fc-pqhx affects the following packages: go.opentelemetry.io/otel/sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-hfvc-g4fc-pqhx?

Update go.opentelemetry.io/otel/sdk to 1.43.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfvc-g4fc-pqhx is resolved across your whole dependency graph.

How do I detect GHSA-hfvc-g4fc-pqhx in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.opentelemetry.io/otel/sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hfvc-g4fc-pqhx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hfvc-g4fc-pqhx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hfvc-g4fc-pqhx can be triaged on real exposure rather than presence alone.

Is GHSA-hfvc-g4fc-pqhx actively exploited in the wild?

No public exploit code has been indexed for GHSA-hfvc-g4fc-pqhx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hfvc-g4fc-pqhx?

GHSA-hfvc-g4fc-pqhx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hfvc-g4fc-pqhx?

GHSA-hfvc-g4fc-pqhx is classified as CWE-426 (CWE-426). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hfvc-g4fc-pqhx published, and has it been updated?

GHSA-hfvc-g4fc-pqhx was published on April 8, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-hfvc-g4fc-pqhx — sdk

GHSA-hfvc-g4fc-pqhx is a CWE-426 vulnerability in go.opentelemetry.io/otel/sdk. A fix is available for go.opentelemetry.io/otel/sdk — see the affected versions and patch details below.

opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking

Also known asCVE-2026-39883GO-2026-5426

Published

Apr 8, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-hfvc-g4fc-pqhx.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹go.opentelemetry.io/otel/sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The fix for GHSA-9h8m-3fm2-qjrq (CVE-2026-24051) changed the Darwin ioreg command to use an absolute path but left the BSD kenv command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms.

Root Cause

sdk/resource/host_id.go line 42:

if result, err := r.execCommand("kenv", "-q", "smbios.system.uuid"); err == nil {

Compare with the fixed Darwin path at line 58:

result, err := r.execCommand("/usr/sbin/ioreg", "-rd1", "-c", "IOPlatformExpertDevice")

The execCommand helper at sdk/resource/host_id_exec.go uses exec.Command(name, arg...) which searches $PATH when the command name contains no path separator.

Affected platforms (per build tag in host_id_bsd.go:4): DragonFly BSD, FreeBSD, NetBSD, OpenBSD, Solaris.

The kenv path is reached when /etc/hostid does not exist (line 38-40), which is common on FreeBSD systems.

Attack

Attacker has local access to a system running a Go application that imports go.opentelemetry.io/otel/sdk
Attacker places a malicious kenv binary earlier in $PATH
Application initializes OpenTelemetry resource detection at startup
hostIDReaderBSD.read() calls exec.Command("kenv", ...) which resolves to the malicious binary
Arbitrary code executes in the context of the application

Same attack vector and impact as CVE-2026-24051.

Suggested Fix

Use the absolute path:

if result, err := r.execCommand("/bin/kenv", "-q", "smbios.system.uuid"); err == nil {

On FreeBSD, kenv is located at /bin/kenv.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.opentelemetry.io/otel/sdk`	≥ 1.15.0&&< 1.43.0	1.43.0`go get go.opentelemetry.io/otel/sdk@v1.43.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.opentelemetry.io/otel/sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.opentelemetry.io/otel/sdk to 1.43.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfvc-g4fc-pqhx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hfvc-g4fc-pqhx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hfvc-g4fc-pqhx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important flaw in OpenTelemetry-Go that allows a local attacker to achieve arbitrary code execution or privilege escalation through PATH hijacking. This vulnerability is specific to BSD and Solaris platforms due to the use of the `kenv` command and does not directly affect Red Hat Enterprise Linux…

Product	Fixed in	Advisory
Cert Manager support for Red Hat OpenShift release 1.19	`cert-manager/cert-manager-istio-csr-rhel9:1788348594`	RHSA-2026:63140
multicluster engine for Kubernetes 2.8	`multicluster-engine/assisted-service-8-rhel8:1781539691`	RHSA-2026:26257
multicluster engine for Kubernetes 2.8	`multicluster-engine/assisted-service-9-rhel9:1781539725`	RHSA-2026:26254
Red Hat Openshift Data Foundation 4.22	`odf4/cephcsi-rhel9:1782932114`	RHSA-2026:37387
Red Hat OpenShift Workload Availability 0.3	`workload-availability/storage-based-remediation-rhel9-operator:1785203474`	RHSA-2026:54286
Red Hat OpenShift Workload Availability 0.8	`workload-availability/fence-agents-remediation-rhel9-operator:1785203079`	RHSA-2026:54274

Frequently Asked Questions

## Summary The fix for GHSA-9h8m-3fm2-qjrq (CVE-2026-24051) changed the Darwin `ioreg` command to use an absolute path but left the BSD `kenv` command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms. ## Root Cause `sdk/resource/host_id.go` line 42: if result, err := r.execCommand("kenv", "-q", "smbios.system.uuid"); err == nil { Compare with the fixed Darwin path at line 58: result, err := r.execCommand("/usr/sbin/ioreg", "-rd1", "-c", "IOPlatformExpertDevice") The `execCommand` helper at `sdk/resource/host_id_exec.go` uses `exec.Command(n

O3 Security · Impact-Aware SCA

Is GHSA-hfvc-g4fc-pqhx in your dependencies?

O3 Security finds GHSA-hfvc-g4fc-pqhx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works