Advisory record · GHSA-799x-qp47-8qwq

Apache Airflow has no certificate validation on SMTP STARTTLS connections

CVSS 5.9 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 1 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
apache-airflowPyPI>=2.0.0, <3.2.23.2.2
Identifiers
GHSA-799x-qp47-8qwq · BIT-airflow-2026-49267 · CVE-2026-49267 · PYSEC-2026-2346
Weakness (CWE)
CWE-295
Published
1 Jun 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Airflow (apache-airflow) versions 2.0.0 before 3.2.2 are affected. When the deployment sets smtp_starttls=True without smtp_ssl, the EmailOperator and airflow.utils.email helpers open STARTTLS connections without validating the SMTP server's certificate. An attacker positioned between the worker and the SMTP server can present a self-signed certificate and capture SMTP credentials and message contents. Upgrade apache-airflow to 3.2.2 or later; users who already applied the SMTP provider fix from CVE-2026-41016 should still upgrade the core package.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 Jun 2026, 07:53 UTC Confirmed by the CVE List
  2. 1 Jun 2026, 09:16 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:43 UTC First seen by agentprime
  4. 31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.