<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: DataDog dd-trace-py</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/datadog-dd-trace-py.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-116589: Datadog dd-trace-py: IAST instrumentation can lead to application DOS</title><link>https://vulnfeed.org/cve/CVE-2026-116589/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116589/</guid><pubDate>Mon, 26 Oct 2026 22:16:55 +0000</pubDate><description>Datadog dd-trace-py is the Datadog Python APM client. From 3.13.0 until 4.15.5, the IAST string-processing instrumentation does not properly handle certain internal errors while old-style % string formatting processes attacker-controlled input. An unhandled error can terminate the Python process and interrupt the work it is handling. Exploitation requires IAST to be enabled, which is not the default, and application code to apply the affected formatting operation to attacker-controlled input. This issue is fixed in version 4.15.5.</description></item><item><title>CVE-2026-116588: Datadog dd-trace-py: ReDOS in URL query string obfuscation</title><link>https://vulnfeed.org/cve/CVE-2026-116588/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116588/</guid><pubDate>Mon, 26 Oct 2026 21:22:46 +0000</pubDate><description>Datadog dd-trace-py is the Datadog Python APM client. From 1.5.0 until 3.19.9 and 4.15.6, the default query-string obfuscation regular expression can exhibit excessive backtracking while synchronously processing attacker-controlled URL query strings for HTTP span metadata. A remote attacker can cause prolonged CPU consumption, request latency, and service unavailability in affected HTTP tracing integrations that include query strings in URL span tags. The vulnerable processing is enabled by default for those integrations. This issue is fixed in versions 3.19.9 and 4.15.6.</description></item></channel></rss>
