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.
CVE-2026-41016
MEDIUMNVD 5.95.9—
EchelonGraph scoreHIGH confidence
Score 5.9 from GitHub Security Advisory published 2026-04-30. NVD baseline CVSS 5.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.9
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EPSS
- 5.8%
- KEV
- Not listed
Published
April 30, 2026
Last Modified
May 1, 2026
References (2)
- security@apachehttps://github.com/apache/airflow/pull/65346
- security@apachehttps://lists.apache.org/thread/gb202qy5r31bgdd3d51d7s5o1jh40kc4
Frequently asked(5)
What is CVE-2026-41016?
CVE-2026-41016 is a medium vulnerability published on April 30, 2026. 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…
When was CVE-2026-41016 disclosed?
CVE-2026-41016 was first published in the National Vulnerability Database on April 30, 2026, with the most recent update on May 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41016 actively exploited?
CVE-2026-41016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41016?
CVE-2026-41016 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-41016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41016
Is Your Infrastructure Affected by CVE-2026-41016?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.