Improper Certificate Validation Affecting airflow-3 package, versions <3.2.1-r4
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-AIRFLOW3-17133252
- published2 Jun 2026
- disclosed30 Apr 2026
Introduced: 30 Apr 2026
CVE-2026-41016 (opens in a new tab)How to fix?
Upgrade Chainguard airflow-3 to version 3.2.1-r4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream airflow-3 package and not the airflow-3 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Apache Airflow's SMTP provider SmtpHook called Python's smtplib.SMTP.starttls() without an SSL context, so no certificate validation was performed on the TLS upgrade. A man-in-the-middle between the Airflow worker and the SMTP server could present a self-signed certificate, complete the STARTTLS upgrade, and capture the SMTP credentials sent during the subsequent login() call. Users are advised to upgrade to the apache-airflow-providers-smtp version that contains the fix.