CVE-2026-41078 | open-telemetry opentelemetry-dotnet/OpenTelemetry.Exporter.Jaeger allocation of resources (GHSA-38h3-2333-qx47)

VDB-359201 · CVE-2026-41078 · GHSA-38H3-2333-QX47 OPEN-TELEMETRY OPENTELEMETRY-DOTNET/OPENTELEMETRY.EXPORTER.JAEGER ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.8 $0-$5k 2.19+ Summaryinfo A vulnerability has been found in open-telemetry opentelemetry-dotnet and OpenTelemetry.Exporter.Jaeger up to 1.6.0-rc.1 and classified as problematic. The impacted element is an unknown function. The manipulation leads to allocation of resources. This vulnerability is documented as CVE-2026-41078. The attack can be initiated remotely. There is not any exploit available. Detailsinfo A vulnerability, which was classified as problematic, has been found in open-telemetry opentelemetry-dotnet and OpenTelemetry.Exporter.Jaeger up to 1.6.0-rc.1. This issue affects an unknown part. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is: 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. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41078 since 04/16/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Vendor open-telemetry Name opentelemetry-dotnet OpenTelemetry.Exporter.Jaeger Version 1.6.0-rc.0 1.6.0-rc.1 Website Product: https://github.com/open-telemetry/opentelemetry-dotnet/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.8 VulDB Meta Temp Score: 4.8 VulDB Base Score: 3.7 VulDB Temp Score: 3.7 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.9 CNA Vector (GitHub_M): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/16/2026 CVE reserved 04/23/2026 +7 days Advisory disclosed 04/23/2026 +0 days VulDB entry created 04/23/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-38h3-2333-qx47 Status: Confirmed CVE: CVE-2026-41078 (🔒) GCVE (CVE): GCVE-0-2026-41078 GCVE (VulDB): GCVE-100-359201 Entryinfo Created: 04/23/2026 23:14 Changes: 04/23/2026 23:14 (61) Complete: 🔍 Cache ID: 99:322:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸