GHSA-p3m5-h5v9-vqj6: Pip/ddtrace vulnerability

Published Oct 27, 2026
·
Updated

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 DDIASTENABLED=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.

Affected Software

1 affected componentFixes available
pip/ddtrace>=3.13.0<4.15.5
4.15.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/ddtrace to a version that resolves this vulnerability.

    Fixed in 4.15.5
  2. Configuration

    Disable IAST by setting DD_IAST_ENABLED=false.

    dd-trace-py IAST DD_IAST_ENABLED = false
  3. Compensating control

    Replace % string interpolations with str.format or f-strings for user inputs in the monitored application.

Event History

Oct 27, 2026
Advisory Published
via GitHub·03:37 PM
Data Sourced
via GitHub·03:37 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service issue?

Only applications using a vulnerable dd-trace-py version with IAST enabled are affected. IAST is disabled by default, so deployments that have not enabled it are not exposed to this issue.

2

What must an attacker be able to do to trigger the issue?

The application must perform an affected string-processing operation on attacker-controlled input while IAST is enabled. Successful triggering can terminate the Python application process, resulting in denial of service.

3

What can be done if upgrading is not immediately possible?

Disable IAST by setting DD_IAST_ENABLED=false. Alternatively, replace replace % string interpolations involving user input in the monitored application with str.format or f-strings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203