High File handling

CVE-2026-24051 — OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking

OpenTelemetry-Go is the Go implementation of OpenTelemetry. The OpenTelemetry Go SDK in version v1.20.0-1.39.0 is vulnerable to Path Hijacking (Untrusted Search Paths) on macOS/Darwin systems. The resource detection code in sdk/resource/host_id.go executes the ioreg system command using a search path. An attacker with the ability to locally modify the PATH environment variable can achieve Arbitrary Code Execution (ACE) within the context of the application. A fix was released with v1.40.0.

Published Feb 2, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 15, 2026

Affects

Open-telemetry

Opentelemetry and 1 more

CVSS base

7.0

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Open-telemetry Opentelemetry, Open-telemetry Opentelemetry-go).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Open-telemetry	Opentelemetry	≥ 1.21.0 and < 1.40.0	Vulnerable	NIST National Vulnerability Database
Open-telemetry	Opentelemetry-go	version >= 1.21.0, < 1.40.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.0	CVSS 3.1	High	1.0	5.9	security-advisories@github.com via NIST National Vulnerability Database
7.0	CVSS 3.1	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-426 · Untrusted Search Path

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Monitor file creation in web directories and paths with traversal sequences (../).

endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · open-telemetry/opentelemetry-go
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 7.0
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Feb 2, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-9h8m-3fm2-qj
Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
github.com/open-telemetry/opentelemetry-go/commit/d45961bcda453fcbdb6469c22d6e88
Patch, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

Open-telemetry
every CVE for this vendor

File handling
same class

CWE-426
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-81869 OpenTelemetry-Go: UTF-8 replacement rune bypasses attribute length truncation 29d
Medium CVE-2026-81872 OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full 29d
Medium CVE-2026-81871 OpenTelemetry-Go: Log gRPC exporter ignores env TLS certs, bypassing mTLS/pinning 29d
Low CVE-2026-81870 OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs 29d
Medium CVE-2026-45404 OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access Aug 24, 2026
Medium CVE-2026-54285 opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation Jun 22, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-24051 is "OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking", rated High. It affects Opentelemetry (Open-telemetry); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.