Vulnerabilities in pkg:nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol

PACKAGE
Advisory Identifier: GHSA-4625-4j76-fww9
Advisory Summary

CVE-2026-42191 is a MODERATE (CVSS 6.5) opentelemetry's disk retry default temp vulnerability (CWE-379: Creation of Temporary File in Directory with Insecure Permissions) affecting OpenTelemetry.Exporter.OpenTelemetryProtocol libraries in the NuGet ecosystem. The issue involves opentelemetry's disk retry default temp path enables local blob injection via otlp exporter. Remediation is available by upgrading affected packages to version 1.15.3.

3 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol

3 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-4625-4j76-fww9 CVE-2026-42191 MODERATE OpenTelemetry's disk retry default temp path enables local blob injection via OTLP Exporter
GHSA-mr8r-92fq-pj8p CVE-2026-40891 MODERATE OpenTelemetry dotnet: Unbounded `grpc-status-details-bin` parsing in OTLP/gRPC retry handling
GHSA-q834-8qmm-v933 CVE-2026-40182 MODERATE OpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies

CVE-2026-42191 at a Glance

CVE Identifier CVE-2026-42191
GHSA Identifier GHSA-4625-4j76-fww9
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-379: Creation of Temporary File in Directory with Insecure Permissions
Affected Product OpenTelemetry.Exporter.OpenTelemetryProtocol
Package Ecosystem NuGet
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-42191

To remediate this vulnerability, upgrade all affected OpenTelemetry.Exporter.OpenTelemetryProtocol dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

OpenTelemetry.Exporter.OpenTelemetryProtocol fixed: 1.15.3
Upgrade OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.15.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for OpenTelemetry.Exporter.OpenTelemetryProtocol

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-42191, inspect your project dependencies for OpenTelemetry.Exporter.OpenTelemetryProtocol:

inspect dependencies for OpenTelemetry.Exporter.OpenTelemetryProtocol

Analyze the terminal output to locate any version of OpenTelemetry.Exporter.OpenTelemetryProtocol in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-379: Creation of Temporary File in Directory with Insecure Permissions, where 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. In OpenTelemetry.Exporter.OpenTelemetryProtocol, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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 exposed three attack surfaces: - **Blob injection (integrity):** an attacker could write crafted `*.blob` files into the predictable path; the exporter picks them up on the next retry cycle and forwards them to the configured OTLP endpoint under the application's identity. - **Telemetry disclosure (confidentiality):** an attacker reads `*.blob` files written by the application between export failures, recovering encoded telemetry payloads (spans, metric data points, log records). - **Resource exhaustion (availability):** an attacker deposits numerous or oversized blob files, degrading retry-loop performance or consuming disk space. ### Details #### Preconditions 1. `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY` is set to `disk`. 2. `OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH` is not set, causing the exporter to resolve the blob storage root using the `System.IO.Path.GetTempPath()` API. 3. A local attacker has read or write access to the process' temporary directory (e.g., `/tmp` on Linux, or `%TEMP%` on a multi-user Windows installation). #### Exploit path 1. A target application starts with `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk` and no explicit blob directory. The exporter resolves the storage root to `Path.GetTempPath()`, producing paths such as `%TEMP%\traces`, `%TEMP%\metrics`, and `%TEMP%\logs` (or `/tmp/traces` etc. on Linux). 2. **Injection scenario:** before or during the application's retry window, an attacker writes crafted `*.blob` files into one of those signal subdirectories. On the next retry interval (by default every 60 seconds), [`OtlpExporterPersistentStorageTransmissionHandler`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/c724f4bd6fd88e9a599af1668bf7af9487155b62/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/Implementation/Transmission/OtlpExporterPersistentStorageTransmissionHandler.cs) scans the directory, loads the attacker-supplied blobs, and forwards them to the configured OTLP endpoint using the application's identity and transport credentials. 3. **Disclosure scenario:** the attacker reads `*.blob` files that the application wrote after a transient export failure, recovering the full serialized telemetry payloads (spans, metric data points, or log records in Protobuf encoding). 5. **DoS scenario:** the attacker deposits a large number of oversized blob files in the temporary subdirectories, causing the retry loop to consume excess CPU/IO processing them, potentially exhausting available disk space. ### Mitigations If an immediate upgrade to a patched version is not possible: 1. Avoid enabling disk retry in shared environments. 2. Configure a dedicated directory with strict ACL/ownership and least privilege. 3. Ensure the directory is not shared across tenants/users. 4. Monitor for unexpected `*.blob` files or abnormal retry backlog growth. ### Resources - [#7106](https://github.com/open-telemetry/opentelemetry-dotnet/pull/7106)

CVE-2026-42191 Affected OpenTelemetry.Exporter.OpenTelemetryProtocol Versions

1 component(s)
Fixed Versions:
1.15.3
Product / Package Ecosystem Affected Versions Fixed Version
OpenTelemetry.Exporter.OpenTelemetryProtocol
NuGet
≥ 1.8.0
< 1.15.3
1.15.3

References

Frequently Asked Questions

What is CVE-2026-42191?
CVE-2026-42191 is a security vulnerability in OpenTelemetry.Exporter.OpenTelemetryProtocol involving OpenTelemetry's disk retry default temp path enables local blob injection via OTLP Exporter under CWE-379: Creation of Temporary File in Directory with Insecure Permissions.
Which OpenTelemetry.Exporter.OpenTelemetryProtocol versions are affected?
Affected versions include releases prior to 1.15.3 across affected packages: OpenTelemetry.Exporter.OpenTelemetryProtocol.
What version fixes CVE-2026-42191?
Upgrading to 1.15.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is OpenTelemetry.Exporter.OpenTelemetryProtocol affected?
Yes, OpenTelemetry.Exporter.OpenTelemetryProtocol is affected in releases prior to 1.15.3. Upgrade your dependency to 1.15.3 or later.
What is the CVSS score of CVE-2026-42191?
CVE-2026-42191 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with CVE-2026-42191?
CVE-2026-42191 is classified under CWE-379: Creation of Temporary File in Directory with Insecure Permissions (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.).
How can I check NuGet dependencies for CVE-2026-42191?
Run the dependency tree command: 'inspect dependencies for OpenTelemetry.Exporter.OpenTelemetryProtocol'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4625-4j76-fww9",
  "modified" : "2026-05-13T16:27:20Z",
  "published" : "2026-04-30T18:34:30Z",
  "aliases" : [ "CVE-2026-42191" ],
  "summary" : "OpenTelemetry's disk retry default temp path enables local blob injection via OTLP Exporter",
  "details" : "### Summary\n\nThe 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.\n\nThe exporter stored and loaded `*.blob` files under fixed, signal-named subdirectories (`traces`, `metrics`, `logs`) beneath that shared temporary root path.\n\nOn multi-user systems where the temporary directory is accessible to other local accounts, this exposed three attack surfaces:\n\n- **Blob injection (integrity):** an attacker could write crafted `*.blob` files into the predictable path; the exporter picks them up on the next retry cycle and forwards them to the configured OTLP endpoint under the application's identity.\n- **Telemetry disclosure (confidentiality):** an attacker reads `*.blob` files written by the application between export failures, recovering encoded telemetry payloads (spans, metric data points, log records).\n- **Resource exhaustion (availability):** an attacker deposits numerous or oversized blob files, degrading retry-loop performance or consuming disk space.\n\n### Details\n\n#### Preconditions\n\n1. `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY` is set to `disk`.\n2. `OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH` is not set, causing the exporter to resolve the blob storage root using the `System.IO.Path.GetTempPath()` API.\n3. A local attacker has read or write access to the process' temporary directory (e.g., `/tmp` on Linux, or `%TEMP%` on a multi-user Windows installation).\n\n#### Exploit path\n\n1. A target application starts with `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk` and no explicit blob directory. The exporter resolves the storage root to `Path.GetTempPath()`, producing paths such as `%TEMP%\\traces`, `%TEMP%\\metrics`, and `%TEMP%\\logs` (or `/tmp/traces` etc. on Linux).\n2. **Injection scenario:** before or during the application's retry window, an attacker writes crafted `*.blob` files into one of those signal subdirectories. On the next retry interval (by default every 60 seconds), [`OtlpExporterPersistentStorageTransmissionHandler`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/c724f4bd6fd88e9a599af1668bf7af9487155b62/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/Implementation/Transmission/OtlpExporterPersistentStorageTransmissionHandler.cs) scans the directory, loads the attacker-supplied blobs, and forwards them to the configured OTLP endpoint using the application's identity and transport credentials.\n3. **Disclosure scenario:** the attacker reads `*.blob` files that the application wrote after a transient export failure, recovering the full serialized telemetry payloads (spans, metric data points, or log records in Protobuf encoding).\n5. **DoS scenario:** the attacker deposits a large number of oversized blob files in the temporary subdirectories, causing the retry loop to consume excess CPU/IO processing them, potentially exhausting available disk space.\n\n### Mitigations\n\nIf an immediate upgrade to a patched version is not possible:\n\n1. Avoid enabling disk retry in shared environments.\n2. Configure a dedicated directory with strict ACL/ownership and least privilege.\n3. Ensure the directory is not shared across tenants/users.\n4. Monitor for unexpected `*.blob` files or abnormal retry backlog growth.\n\n### Resources\n\n- [#7106](https://github.com/open-telemetry/opentelemetry-dotnet/pull/7106)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "OpenTelemetry.Exporter.OpenTelemetryProtocol"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.8.0"
      }, {
        "fixed" : "1.15.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.15.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-4625-4j76-fww9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42191"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/7106"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/commit/78dffdc5ebdf3dc090fdb94e3f1a32d3d1e26dfd"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-379" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-30T18:34:30Z",
    "nvd_published_at" : "2026-05-12T20:16:41Z"
  }
}