{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50275 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50275 is a high-severity denial of service vulnerability in DataDog dd-trace-php, 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-50275 and fix it if it is affected.\n\nWhat it is: CVE-2026-50275 is a high-severity denial of service vulnerability in DataDog dd-trace-php, 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-50275 in the wild and no public exploit code.\n\nAffected product: DataDog dd-trace-php. 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-50275/ (Markdown: https://insights.sbomify.com/CVE-2026-50275/index.md)","id":"CVE-2026-50275","markdown":"https://insights.sbomify.com/CVE-2026-50275/index.md","name":"CVE-2026-50275","record":{"aliases":["GHSA-phwx-ww2p-cv9v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Datadog PHP Tracer","requires_auth":"none","summary":"Remote attackers can cause denial of service by sending oversized W3C baggage headers to applications using the Datadog PHP Tracer.","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":"The Datadog PHP Tracer provides application performance monitoring and distributed tracing for PHP. Prior to 1.19.2, ddtrace_deserialize_baggage in ext/distributed_tracing_headers.c parses incoming W3C baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES. A remote unauthenticated client can send an arbitrarily large number of comma-separated key-value pairs or a single oversized value, causing the tracer to allocate hash-map entries and consume unbounded CPU and memory on each request. Baggage extraction is enabled by default in most affected deployments unless baggage is removed from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT. This issue is fixed in version 1.19.2.","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":"Datadog PHP Tracer: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"dd-trace-rb: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50276"},"packages":[],"prev":{"headline":"dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS","id":"CVE-2026-50274"},"products":["dd-trace-php"],"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-18","vendors":["DataDog"]},"summary":"Remote attackers can cause denial of service by sending oversized W3C baggage headers to applications using the Datadog PHP Tracer.","url":"https://insights.sbomify.com/CVE-2026-50275/"}