CVE-2026-116589: Datadog dd-trace-py: IAST instrumentation can lead to application DOS
CVE-2026-116589 lets an attacker crash a Python application that uses Datadog's ddtrace (dd-trace-py) with IAST enabled. Attacker-controlled text reaching an instrumented string operation terminates the process. Versions 3.13.0 up to 4.15.4 are affected. Upgrade to 4.15.5. IAST is off by default.
Published Oct 27, 2026 · Analysis Nov 1, 2026
What an attacker can do
IAST (Interactive Application Security Testing) in ddtrace instruments string operations to track tainted input. The advisory says this instrumentation does not handle certain internal errors, so an error can end the whole Python process. The 4.15.5 release notes describe the trigger: taint tracking could abort the process when old-style % string formatting handled tainted text containing a lone surrogate character.
Two conditions must hold. IAST must be enabled, and application code must run an affected string operation on attacker-controlled input. An unauthenticated remote attacker who can send such input, for example in a request parameter that ends up in a % format string, can kill the worker. Repeated requests keep workers down and interrupt work in progress. The impact is availability only; the CVSS 4.0 vector shows no confidentiality or integrity loss. The attack-requirements flag (AT:P) reflects the IAST precondition.
Who is affected
The pip package ddtrace, versions >= 3.13.0 and < 4.15.5, and only when IAST is turned on (DD_IAST_ENABLED). Applications with IAST at its default off setting are not exposed by this flaw.
Check the installed version:
pip show ddtraceThen check whether DD_IAST_ENABLED is set to true in your environment or deployment config.
ddtrace
- Ecosystem
- PyPI
- Affected
- >= 3.13.0, < 4.15.5
- Fixed in
- 4.15.5
- Check
pip show ddtrace
How to fix it
Upgrade to ddtrace 4.15.5:
pip install --upgrade "ddtrace>=4.15.5"If you cannot upgrade yet, the advisory gives two workarounds: set DD_IAST_ENABLED=false, or replace % string interpolation with str.format or f-strings wherever user input is formatted in monitored code. The fix is in pull requests 20786 and 20823.
How to tell if you were hit
Look for unexplained exits or restarts of Python workers (gunicorn, uWSGI, Celery or container restarts) that line up with requests carrying unusual text, especially non-ASCII or lone surrogate characters, in inputs that reach % formatting. Check the process manager's logs for abrupt terminations without a normal Python traceback. The advisory leaves out trigger inputs, so no exact signature exists.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
A flaw in dd-trace-py’s IAST instrumentation can cause the Python application process to terminate unexpectedly when processing certain attacker-controlled input. Only applications with IAST enabled are affected. IAST is disabled by default.
Details
The affected IAST string-processing instrumentation does not properly handle certain internal errors, allowing an error to terminate the application process. Exploitation requires IAST to be enabled and application code to perform an affected string-processing operation on attacker-controlled input.
If you are unable to upgrade to a patched version of dd-trace-py, you can mitigate this issue by either disabling IAST (setting DD_IAST_ENABLED=false) or by replacing replace % string interpolations with str.format or f-strings for user inputs in your monitored application.
Proof of concept
Detailed triggering inputs and reproduction steps are omitted from this advisory. The linked fix (#20786) includes regression coverage for the affected behavior.
Impact
Denial of service affecting applications that use a vulnerable version of dd-trace-py with IAST enabled and expose the affected operation to attacker-controlled input. Successful exploitation terminates the affected Python process and interrupts the work it is handling.
Questions
- Is ddtrace affected if I never enabled IAST?
No. The advisory says only applications with IAST enabled are affected, and IAST is disabled by default. Check that DD_IAST_ENABLED is not set to true.
- Which ddtrace version fixes CVE-2026-116589?
ddtrace 4.15.5. Affected releases run from 3.13.0 up to, but not including, 4.15.5.
- Can this lead to code execution or data theft?
No. The advisory describes a denial of service: the Python process terminates. The CVSS vector has no confidentiality or integrity impact.
- What can I do without upgrading?
Set DD_IAST_ENABLED=false, or switch % string interpolation on user input to str.format or f-strings, as the advisory suggests.
References
Read for this analysis:
- https://github.com/DataDog/dd-trace-py/security/advisories/GHSA-p3m5-h5v9-vqj6
- https://github.com/DataDog/dd-trace-py/releases/tag/v4.15.5
- https://nvd.nist.gov/vuln/detail/CVE-2026-116589
- https://github.com/DataDog/dd-trace-py/pull/20786
- https://github.com/DataDog/dd-trace-py/pull/20823
- https://github.com/DataDog/dd-trace-py/commit/69dc19853247434ceab83e0c1c4e279a2eb2a3f7
- https://github.com/DataDog/dd-trace-py/commit/ace972489b57dd020ff52b706bb548a354f2dd69
- https://github.com/advisories/GHSA-p3m5-h5v9-vqj6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
