Apache Airflow's SMTP provider called Python's without an SSL context, so no certificate validation was performed on the TLS upgrade.

Code

The project this record applies to. Exploit listings stay in References.

• Repository · github.com

Timeline

Detection, updates, and resolution for this record.

1. Apr 30, 2026 · NIST NVD

   Detected

   Apache Airflow's SMTP provider called Python's 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 call. Users are advised to upgrade to the version that contains the

2. Jun 17, 2026 · NIST NVD

   Updated

   Apache Airflow's SMTP provider called Python's 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 call. Users are advised to upgrade to the version that contains the

Affected

• cpe apache/airflowversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-41016

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-41016

  Apache Airflow's SMTP provider called Python's 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, c

  nvd.nist.gov

References

• Issue Tracking · github.com
• Mailing List · lists.apache.org