dbcve.org
OpentelemetryApplication

CVE-2026-41078

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenTelemetry dotnet is a dotnet telemetry framework. In 1.6.0-rc.1 and earlier, 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. There is no plan to fix this issue as OpenTelemetry.Exporter.Jaeger was deprecated in 2023.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenTelemetry.Exporter.Jaeger versions 1.6.0-rc.1 and earlier suffer from unbounded memory growth. The internal pooled-list sizing algorithm expands based on large observed span or tag sets and reuses that enlarged allocation size for subsequent operations, causing sustained memory pressure under high-cardinality or attacker-controlled telemetry input, potentially leading to denial of service.

MitigationMigrate away from OpenTelemetry.Exporter.Jaeger to a supported OpenTelemetry exporter (such as OTLP, Zipkin, or Prometheus), as this deprecated component will not receive a fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpentelemetryApplication
Affected:< 1.6.0= 1.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jaeger exporter package usage
    Search project files (.csproj, packages.config) and NuGet references for 'OpenTelemetry.Exporter.Jaeger' or 'opentelemetry.exporter.jaeger'
    Affected if The package is referenced in the project dependencies
  2. Determine installed package version
    Run 'dotnet list package' or inspect the Version property in the .csproj file for the OpenTelemetry.Exporter.Jaeger reference
    Affected if The version is 1.6.0-rc.1 or earlier, or exactly 1.6.0
  3. Verify Jaeger exporter is instantiated
    Search source code for 'new JaegerExporter' or 'using OpenTelemetry.Exporter.Jaeger' to confirm the exporter is actually created at runtime
    Affected if The vulnerable code path is executed in the application
  4. Check for high-cardinality telemetry input
    Review whether the application processes external or untrusted span/tag data that could contain large cardinality values
    Affected if Untrusted telemetry input can trigger the unbounded memory growth

A user is affected if they use OpenTelemetry.Exporter.Jaeger version 1.6.0-rc.1 or earlier (including 1.6.0) and that exporter processes telemetry data

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Migrate away from OpenTelemetry.Exporter.Jaeger to a supported OpenTelemetry exporter (such as OTLP, Zipkin, or Prometheus), as this deprecated component will not receive a fix.

Recommended fix High confidence
  1. 1. Migrate away from OpenTelemetry.Exporter.Jaeger as it was deprecated in 2023 and has no planned fix for this vulnerability.
  2. 2. Replace Jaeger exporter with an alternative supported exporter such as OpenTelemetry.Exporter.Prometheus, OpenTelemetry.Exporter.Zipkin, or OpenTelemetry.Exporter.OpenTelemetryProtocol (OTLP).
  3. 3. Update project dependencies to remove the deprecated Jaeger exporter package.
  4. 4. Reconfigure your telemetry pipeline to use the new exporter endpoint.
Caveat Migration to a different exporter is required as Jaeger exporter is deprecated with no security patches coming

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opentelemetry Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41078 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data