{"answers":{"affected":"3 open source packages ship an affected version, including ddtrace.","exploited":"There is no known exploitation of CVE-2026-50271 in the wild and no public exploit code.","fix":"Upgrade ddtrace to 4.8.2 or later.","what":"CVE-2026-50271 is a high-severity denial of service vulnerability in DataDog dd-trace-py, 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-50271 and fix it if it is affected.\n\nWhat it is: CVE-2026-50271 is a high-severity denial of service vulnerability in DataDog dd-trace-py, 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-50271 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ddtrace (PyPI): affected all versions; fixed in 4.8.2\n- ddtrace (PyPI): affected all versions; fixed in 4.8.2\n- ddtrace (PyPI): affected all versions; fixed in 4.8.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-50271/ (Markdown: https://insights.sbomify.com/CVE-2026-50271/index.md)","id":"CVE-2026-50271","markdown":"https://insights.sbomify.com/CVE-2026-50271/index.md","name":"CVE-2026-50271","record":{"aliases":["CLEANSTART-2026-LJ45611","ECHO-3720-ec23-e2d2","GHSA-mw54-j2v2-42hr","MINI-2j8x-g7r5-fmp9","MINI-7cpj-j3j8-wr8x","MINI-7w5v-m3wj-2rch","MINI-8f69-rprh-pr6r","MINI-93cp-74r3-mcxf","MINI-9rmp-3778-rrrw","MINI-c5pv-q246-crpw","MINI-chp3-m7cp-44m3","MINI-f72m-qggf-c34g","MINI-g7gj-wpcj-qx83","MINI-jh94-g5cp-mj88","MINI-jp3j-w58r-w3xg","MINI-qfhf-42c4-4483","MINI-qg98-83hf-mjmx","MINI-qjf3-wgg5-hq43","MINI-r5v7-q88f-3m8c","PYSEC-2026-3461","ROOT-APP-PYPI-CVE-2026-50271"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python APM client","requires_auth":"none","summary":"Remote attackers can cause denial of service in Datadog Python APM clients by sending oversized W3C baggage headers that bypass resource limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Datadog dd-trace-py is the Datadog Python APM client. Prior to 4.8.2, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES limits on the extract path. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs or a single very large value, causing unbounded CPU and memory consumption and enabling a remote denial of service against HTTP services with baggage propagation enabled. This issue is fixed in version 4.8.2.","ecosystems":["PyPI"],"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":"dd-trace-py: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"dd-trace: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50272"},"packages":[{"ecosystem":"PyPI","fixed":["4.8.2"],"introduced":["0"],"last_affected":[],"package":"ddtrace","purl":null,"source":"GHSA-mw54-j2v2-42hr"},{"ecosystem":"PyPI","fixed":["4.8.2"],"introduced":["0"],"last_affected":[],"package":"ddtrace","purl":"pkg:pypi/ddtrace","source":"GHSA-mw54-j2v2-42hr"},{"ecosystem":"PyPI","fixed":["4.8.2"],"introduced":["0"],"last_affected":[],"package":"ddtrace","purl":"pkg:pypi/ddtrace","source":"PYSEC-2026-3461"}],"prev":{"headline":"dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50270"},"products":["dd-trace-py"],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":["DataDog"]},"summary":"Remote attackers can cause denial of service in Datadog Python APM clients by sending oversized W3C baggage headers that bypass resource limits.","url":"https://insights.sbomify.com/CVE-2026-50271/"}