{"answers":{"affected":"2 open source packages ship an affected version, including opentelemetry_sdk.","exploited":"There is no known exploitation of CVE-2026-48504 in the wild and no public exploit code.","fix":"Upgrade opentelemetry_sdk to 0.32.1 or later.","what":"CVE-2026-48504 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-rust, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48504 and fix it if it is affected.\n\nWhat it is: CVE-2026-48504 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-rust, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48504 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- opentelemetry_sdk (crates.io): affected all versions; fixed in 0.32.1\n- opentelemetry_sdk (crates.io): affected all versions; fixed in 0.32.1\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-48504/ (Markdown: https://insights.sbomify.com/CVE-2026-48504/index.md)","id":"CVE-2026-48504","markdown":"https://insights.sbomify.com/CVE-2026-48504/index.md","name":"CVE-2026-48504","record":{"aliases":["GHSA-w9wp-h8wv-79jx","MINI-3v73-q5m6-3924","MINI-45rf-p35g-c9p2","MINI-7x42-3339-69rw","MINI-hq6r-8qqj-xrcm","MINI-j2c4-qgxm-r5x8","MINI-w56v-hmh8-vvpq","MINI-xj5h-q8v9-625m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenTelemetry Rust library","requires_auth":"none","summary":"Attackers can cause resource exhaustion in services using OpenTelemetry Rust by sending oversized W3C Baggage headers, leading to increased CPU and memory usage.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"OpenTelemetry Rust is the Rust OpenTelemetry implementation. In 0.32.0 and earlier, BaggagePropagator::extract_with_context in opentelemetry_sdk did not enforce W3C Baggage size limits before parsing an inbound baggage header, so a large attacker-controlled header could cause unnecessary CPU work and short-lived heap allocations while parsing entries later discarded by the SDK's baggage storage limits. Services that accept untrusted inbound propagation headers may experience increased per-request resource usage when processing oversized baggage headers. This issue is fixed in version 0.32.1.","ecosystems":["crates.io"],"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 Rust: Unbounded memory allocation in W3C Baggage propagation","id":"CVE-2026-48504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission","id":"CVE-2026-48505"},"packages":[{"ecosystem":"crates.io","fixed":["0.32.1"],"introduced":["0"],"last_affected":[],"package":"opentelemetry_sdk","purl":null,"source":"GHSA-w9wp-h8wv-79jx"},{"ecosystem":"crates.io","fixed":["0.32.1"],"introduced":["0"],"last_affected":[],"package":"opentelemetry_sdk","purl":"pkg:cargo/opentelemetry_sdk","source":"GHSA-w9wp-h8wv-79jx"}],"prev":{"headline":"Information disclosure in libiec61850","id":"CVE-2026-48503"},"products":["opentelemetry-rust"],"published":"2026-07-17","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["open-telemetry"]},"summary":"Attackers can cause resource exhaustion in services using OpenTelemetry Rust by sending oversized W3C Baggage headers, leading to increased CPU and memory usage.","url":"https://insights.sbomify.com/CVE-2026-48504/"}