CVE-2026-49267: CWE-295: Improper Certificate Validation in Apache Software Foundation Apache Airflow
Apache Airflow's EmailOperator and the underlying `airflow.utils.email` helpers established SMTP STARTTLS connections without verifying the remote certificate when the deployment used `[email] smtp_starttls=True` without `[email] smtp_ssl`. An attacker positioned between the worker and the configured SMTP server (network MITM — typical hostile-network attack-surface for environments where the SMTP relay sits outside the worker's trust boundary) could present a self-signed certificate, have the worker complete the STARTTLS handshake silently, and capture the SMTP AUTH credentials and message contents the worker forwarded. This CVE covers the **core apache-airflow side** of the same root cause already covered for the SMTP provider by `CVE-2026-41016` (published 2026-04-27, covering `apache-airflow-providers-smtp`). Users who already applied the SMTP-provider fix from CVE-2026-41016 should additionally upgrade `apache-airflow` to 3.2.2 or later to cover the core-side path through `airflow.utils.email`. Affects deployments configured with `smtp_starttls=True` and `smtp_ssl=False` where the SMTP relay is reachable across a less-trusted network segment than the worker. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
AI Analysis
Technical Summary
CVE-2026-49267 is an improper certificate validation vulnerability (CWE-295) in Apache Airflow's core email functionality. When Airflow is configured with smtp_starttls=True and smtp_ssl=False, the EmailOperator and airflow.utils.email helpers establish SMTP STARTTLS connections without verifying the remote server's TLS certificate. This allows a man-in-the-middle attacker on the network path between the Airflow worker and the SMTP server to present a self-signed certificate, causing the worker to complete the TLS handshake silently and expose SMTP authentication credentials and email content. This vulnerability affects Airflow versions starting from 2.0.0 and is fixed in version 3.2.2. It complements a related fix in the SMTP provider package (CVE-2026-41016).
Potential Impact
An attacker capable of intercepting network traffic between the Airflow worker and the SMTP server can exploit this vulnerability to capture SMTP authentication credentials and email message contents. This compromises the confidentiality of email communications sent by Airflow and potentially allows unauthorized access to the SMTP server. The vulnerability only affects deployments using STARTTLS without SSL where the SMTP relay is reachable across a less-trusted network segment than the worker.
Mitigation Recommendations
Users should upgrade Apache Airflow to version 3.2.2 or later to address this vulnerability. If the related SMTP provider package fix (CVE-2026-41016) has already been applied, upgrading Airflow itself is still necessary to cover the core-side email path. There is no indication that temporary mitigations or workarounds are sufficient. Patch status is not explicitly stated but the vendor advises upgrading to 3.2.2 or later, indicating an official fix is available in that version.
CVE-2026-49267: CWE-295: Improper Certificate Validation in Apache Software Foundation Apache Airflow
Description
Apache Airflow's EmailOperator and the underlying `airflow.utils.email` helpers established SMTP STARTTLS connections without verifying the remote certificate when the deployment used `[email] smtp_starttls=True` without `[email] smtp_ssl`. An attacker positioned between the worker and the configured SMTP server (network MITM — typical hostile-network attack-surface for environments where the SMTP relay sits outside the worker's trust boundary) could present a self-signed certificate, have the worker complete the STARTTLS handshake silently, and capture the SMTP AUTH credentials and message contents the worker forwarded. This CVE covers the **core apache-airflow side** of the same root cause already covered for the SMTP provider by `CVE-2026-41016` (published 2026-04-27, covering `apache-airflow-providers-smtp`). Users who already applied the SMTP-provider fix from CVE-2026-41016 should additionally upgrade `apache-airflow` to 3.2.2 or later to cover the core-side path through `airflow.utils.email`. Affects deployments configured with `smtp_starttls=True` and `smtp_ssl=False` where the SMTP relay is reachable across a less-trusted network segment than the worker. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-49267 is an improper certificate validation vulnerability (CWE-295) in Apache Airflow's core email functionality. When Airflow is configured with smtp_starttls=True and smtp_ssl=False, the EmailOperator and airflow.utils.email helpers establish SMTP STARTTLS connections without verifying the remote server's TLS certificate. This allows a man-in-the-middle attacker on the network path between the Airflow worker and the SMTP server to present a self-signed certificate, causing the worker to complete the TLS handshake silently and expose SMTP authentication credentials and email content. This vulnerability affects Airflow versions starting from 2.0.0 and is fixed in version 3.2.2. It complements a related fix in the SMTP provider package (CVE-2026-41016).
Potential Impact
An attacker capable of intercepting network traffic between the Airflow worker and the SMTP server can exploit this vulnerability to capture SMTP authentication credentials and email message contents. This compromises the confidentiality of email communications sent by Airflow and potentially allows unauthorized access to the SMTP server. The vulnerability only affects deployments using STARTTLS without SSL where the SMTP relay is reachable across a less-trusted network segment than the worker.
Mitigation Recommendations
Users should upgrade Apache Airflow to version 3.2.2 or later to address this vulnerability. If the related SMTP provider package fix (CVE-2026-41016) has already been applied, upgrading Airflow itself is still necessary to cover the core-side email path. There is no indication that temporary mitigations or workarounds are sufficient. Patch status is not explicitly stated but the vendor advises upgrading to 3.2.2 or later, indicating an official fix is available in that version.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-28T16:39:15.393Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e79e29bf47b50cd4b53
Added to database: 6/1/2026, 9:18:49 AM
Last enriched: 6/1/2026, 9:34:58 AM
Last updated: 6/2/2026, 7:26:40 AM
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.