open-telemetry opentelemetry-dotnet up to 1.15.2 Path.GetTempPath temp file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in open-telemetry opentelemetry-dotnet up to 1.15.2. This affects the function Path.GetTempPath. Such manipulation leads to temp file.
This vulnerability is listed as CVE-2026-42191. The attack must be carried out locally. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability was found in open-telemetry opentelemetry-dotnet up to 1.15.2. It has been rated as problematic. Affected by this issue is the function Path.GetTempPath. The manipulation with an unknown input leads to a temp file vulnerability. Using CWE to declare the problem leads to CWE-379. The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file. Impacted is confidentiality, integrity, and availability. CVE summarizes:
OpenTelemetry.Exporter.OpenTelemetryProtocol is the OTLP (OpenTelemetry Protocol) exporter implementation. From 1.8.0 to 1.15.2, the OTLP disk retry feature in OpenTelemetry.Exporter.OpenTelemetryProtocol silently fell back to Path.GetTempPath() when OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk was set but OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH was not configured. The exporter stored and loaded *.blob files under fixed, signal-named subdirectories (traces, metrics, logs) beneath that shared temporary root path. On multi-user systems where the temporary directory is accessible to other local accounts, this allows an attacker to write crafted *.blob files, read *.blob files written by the application between export failures, or deposit numerous or oversized blob files, degrading retry-loop performance or consuming disk space. This vulnerability is fixed in 1.15.3.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-42191 since 04/25/2026. The exploitation is known to be difficult. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
Upgrading to version 1.15.3 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Temp fileCWE: CWE-379 / CWE-377
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: opentelemetry-dotnet 1.15.3
Timeline
04/25/2026 CVE reserved05/12/2026 Advisory disclosed
05/12/2026 VulDB entry created
05/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-42191 (🔒)
GCVE (CVE): GCVE-0-2026-42191
GCVE (VulDB): GCVE-100-363338
Entry
Created: 05/12/2026 22:03Updated: 05/27/2026 15:11
Changes: 05/12/2026 22:03 (63), 05/27/2026 15:11 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.