Improper Certificate Validation Affecting datadog-agent-7.77 package, versions <7.77.3-r27


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.24% (14th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-DATADOGAGENT777-20414070
  • published3 Oct 2026
  • disclosed29 Sept 2026

Introduced: 29 Sep 2026

NewCVE-2026-97687  (opens in a new tab)
CWE-295  (opens in a new tab)
CWE-440  (opens in a new tab)

How to fix?

Upgrade Chainguard datadog-agent-7.77 to version 7.77.3-r27 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream datadog-agent-7.77 package and not the datadog-agent-7.77 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.

CVSS Base Scores

version 3.1