Opentelemetry.Exporter.Jaeger
Approved changes feed: RSS · Atom
cpe:2.3:a:open-telemetry:opentelemetry.exporter.jaeger:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Open Telemetry (e0933b97-2767-54e8-948d-aac7569a5839) |
|---|---|
| Product | Opentelemetry.Exporter.Jaeger (080f9886-28ff-5b3f-808e-8767fe7960af) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-41078 |
vulnerable | 2026-06-03 15:23:35.499323 |
OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path
MEDIUM (5.9)
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.
Published: 2026-04-23T18:05:41.367Z
Updated: 2026-04-23T18:52:26.466Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.