{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50277 is a high-severity denial of service vulnerability in DataDog dd-trace-cpp, published on 17 Sep 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-50277 and fix it if it is affected.\n\nWhat it is: CVE-2026-50277 is a high-severity denial of service vulnerability in DataDog dd-trace-cpp, published on 17 Sep 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-50277 in the wild and no public exploit code.\n\nAffected product: DataDog dd-trace-cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-50277/ (Markdown: https://insights.sbomify.com/CVE-2026-50277/index.md)","id":"CVE-2026-50277","markdown":"https://insights.sbomify.com/CVE-2026-50277/index.md","name":"CVE-2026-50277","record":{"aliases":["GHSA-ch7h-phmx-rqwq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Datadog tracing library","requires_auth":"none","summary":"Remote attackers can cause denial of service in services using dd-trace-cpp by sending oversized W3C baggage headers, leading to resource exhaustion.","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":"dd-trace-cpp is the Datadog distributed tracing library for C++. Prior to 2.1.0, dd-trace-cpp parses incoming W3C baggage headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on the extraction path, even though those limits are enforced during injection. A remote unauthenticated attacker can send a header containing many comma-separated key-value pairs or one very large value, causing per-request hash-map allocation and unbounded CPU and memory consumption. Baggage extraction is enabled by default in most affected tracers unless baggage is removed from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT, so affected internet-facing services can be denied service. This issue is fixed in version 2.1.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"dd-trace-cpp: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"iccDEV: CIccEmbedIO::Read8() size_t underflow","id":"CVE-2026-50278"},"packages":[],"prev":{"headline":"dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50276"},"products":["dd-trace-cpp"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-21","vendors":["DataDog"]},"summary":"Remote attackers can cause denial of service in services using dd-trace-cpp by sending oversized W3C baggage headers, leading to resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-50277/"}