CVE-2026-41078: OpenTelemetry.Exporter.Jaeger OpenTelemetry .NET Has Potential Memory Vulnerability
MODERATECVE-2026-41078 is a MODERATE (CVSS 5.9) opentelemetry .net has potential memory vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting OpenTelemetry.Exporter.Jaeger libraries in the NuGet ecosystem. The issue involves opentelemetry .net has potential memory exhaustion via unbounded pooled-list sizing in jaeger exporter conversion path. Remediation is available in the latest vendor maintenance releases.
CVE-2026-41078 at a Glance
Security Impact
CVSS: 5.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-41078
To remediate this vulnerability, upgrade all affected OpenTelemetry.Exporter.Jaeger dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade OpenTelemetry.Exporter.Jaeger to Latest secure releaseRun the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for OpenTelemetry.Exporter.JaegerHow to Check if You Are Affected
To determine whether your application is affected by CVE-2026-41078, inspect your project dependencies for OpenTelemetry.Exporter.Jaeger:
inspect dependencies for OpenTelemetry.Exporter.JaegerAnalyze the terminal output to locate any version of OpenTelemetry.Exporter.Jaeger in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), 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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In OpenTelemetry.Exporter.Jaeger, 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
CVE-2026-41078 Affected OpenTelemetry.Exporter.Jaeger Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
OpenTelemetry.Exporter.Jaeger
|
NuGet |
≤ 1.6.0-rc.1
|
|
References
Frequently Asked Questions
What is CVE-2026-41078?
Which OpenTelemetry.Exporter.Jaeger versions are affected?
What version fixes CVE-2026-41078?
Is OpenTelemetry.Exporter.Jaeger affected?
What is the CVSS score of CVE-2026-41078?
What CWE is associated with CVE-2026-41078?
How can I check NuGet dependencies for CVE-2026-41078?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-38h3-2333-qx47",
"modified" : "2026-04-27T16:15:48Z",
"published" : "2026-04-18T01:05:12Z",
"aliases" : [ "CVE-2026-41078" ],
"summary" : "OpenTelemetry .NET has potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path",
"details" : "### Summary\n\n> [!IMPORTANT] \n> There is no plan to fix this issue as `OpenTelemetry.Exporter.Jaeger` was deprecated in 2023. It is for informational purposes only.\n\n`OpenTelemetry.Exporter.Jaeger` may allow sustained memory pressure when the internal pooled-list sizing grows based on a large observed span/tag set and that enlarged size is reused for subsequent allocations. Under high-cardinality or attacker-influenced telemetry input, this can increase memory consumption and potentially cause denial of service.\n\n### Details\n\nThe Jaeger exporter conversion path can append tag/event data into pooled list structures. In affected versions, pooled allocation sizing may be influenced by large observed payloads and reused globally across later allocations, resulting in persistent oversized rentals and elevated memory pressure. In environments where telemetry attributes/events can be influenced by untrusted input and limits are increased from defaults, this may lead to process instability or denial of service.\n\n### Impact\n\nAvailability impact only. Confidentiality and integrity impacts are not expected.\n\n### Workarounds / Mitigations\n\n* Prefer maintained exporters (for example OpenTelemetry Protocol format (OTLP)) instead of the Jaeger exporter.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "NuGet",
"name" : "OpenTelemetry.Exporter.Jaeger"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.6.0-rc.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-38h3-2333-qx47"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41078"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/open-telemetry/opentelemetry-dotnet"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-770" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-18T01:05:12Z",
"nvd_published_at" : "2026-04-23T19:17:28Z"
}
}