{"answers":{"affected":"2 open source packages ship an affected version, including OpenTelemetry.Exporter.OpenTelemetryProtocol. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40182 in the wild and no public exploit code.","fix":"Upgrade OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.15.2 or later.","what":"CVE-2026-40182 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40182 and fix it if it is affected.\n\nWhat it is: CVE-2026-40182 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40182 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- OpenTelemetry.Exporter.OpenTelemetryProtocol (NuGet): affected from 1.13.1; fixed in 1.15.2\n- OpenTelemetry.Exporter.OpenTelemetryProtocol (NuGet): affected from 1.13.1; fixed in 1.15.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40182/ (Markdown: https://insights.sbomify.com/CVE-2026-40182/index.md)","id":"CVE-2026-40182","markdown":"https://insights.sbomify.com/CVE-2026-40182/index.md","name":"CVE-2026-40182","record":{"aliases":["GHSA-q834-8qmm-v933","MINI-69f7-p9h3-5xwr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenTelemetry dotnet library","requires_auth":"none","summary":"An attacker can cause memory exhaustion in applications using OpenTelemetry dotnet by returning large error responses from a compromised or MitM'd telemetry backend.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opentelemetry","vendor":"opentelemetry"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 to before 1.15.2, When exporting telemetry to a back-end/collector over gRPC or HTTP using OpenTelemetry Protocol format (OTLP), if the request results in a unsuccessful request (i.e. HTTP 4xx or 5xx), the response is read into memory with no upper-bound on the number of bytes consumed. This could cause memory exhaustion in the consuming application if the configured back-end/collector endpoint is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response. This vulnerability is fixed in 1.15.2.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies","id":"CVE-2026-40182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"ImageMagick: Heap buffer overflow when encoding JXL image with a 16-bit float","id":"CVE-2026-40183"},"packages":[{"ecosystem":"NuGet","fixed":["1.15.2"],"introduced":["1.13.1"],"last_affected":[],"package":"OpenTelemetry.Exporter.OpenTelemetryProtocol","purl":null,"source":"GHSA-q834-8qmm-v933"},{"ecosystem":"NuGet","fixed":["1.15.2"],"introduced":["1.13.1"],"last_affected":[],"package":"OpenTelemetry.Exporter.OpenTelemetryProtocol","purl":"pkg:nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol","source":"GHSA-q834-8qmm-v933"}],"prev":{"headline":"React Router's same-origin redirect with path starting // causes open redirect via protocol-relative URL reinterpretation","id":"CVE-2026-40181"},"products":["opentelemetry-dotnet"],"published":"2026-04-23","related":[{"cvss_score":7.5,"headline":"OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)","id":"CVE-2026-29181","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":7.5,"headline":"DoS vulnerability in otelgrpc (uncontrolled resource consumption) due to unbound cardinality metrics","id":"CVE-2023-47108","kev_date_added":null,"published":"2023-11-10"},{"cvss_score":7.5,"headline":"OpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics","id":"CVE-2023-45142","kev_date_added":null,"published":"2023-10-12"},{"cvss_score":7.5,"headline":"opentelemetry-instrumentation Denial of Service vulnerability due to unbound cardinality metrics","id":"CVE-2023-43810","kev_date_added":null,"published":"2023-10-06"},{"cvss_score":7.3,"headline":"opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking","id":"CVE-2026-39883","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7,"headline":"OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking","id":"CVE-2026-24051","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":5.9,"headline":"OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path","id":"CVE-2026-41078","kev_date_added":null,"published":"2026-04-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["open-telemetry"]},"summary":"An attacker can cause memory exhaustion in applications using OpenTelemetry dotnet by returning large error responses from a compromised or MitM'd telemetry backend.","url":"https://insights.sbomify.com/CVE-2026-40182/"}