You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: Apache Airflow de Apache Software Foundation, Description: El EmailOperator de Apache Airflow y las funciones auxiliares subyacentes 'airflow.utils.email' establecían conexiones SMTP STARTTLS sin verificar el certificado remoto cuando la implementación utilizaba '[email] smtp_starttls=True' sin '[email] smtp_ssl'. Un atacante posicionado entre el worker y el servidor SMTP configurado (MitM de red - superficie de ataque típica de red hostil para entornos donde el relé SMTP se encuentra fuera del límite de confianza del worker) podría presentar un certificado autofirmado, hacer que el worker completara el handshake STARTTLS silenciosamente, y capturar las credenciales SMTP AUTH y el contenido del mensaje que el worker reenviaba.
Este CVE cubre el lado central de apache-airflow de la misma causa raíz ya cubierta para el proveedor SMTP por 'CVE-2026-41016' (publicado el 27-04-2026, cubriendo 'apache-airflow-providers-smtp'). Los usuarios que ya aplicaron la corrección del proveedor SMTP de CVE-2026-41016 deberían actualizar adicionalmente 'apache-airflow' a 3.2.2 o posterior para cubrir la ruta del lado central a través de 'airflow.utils.email'. Afecta a las implementaciones configuradas con 'smtp_starttls=True' y 'smtp_ssl=False' donde el relé SMTP es accesible a través de un segmento de red menos confiable que el worker.
Se aconseja a los usuarios actualizar a 'apache-airflow' 3.2.2 o posterior.
New CVE Received from Apache Software Foundation6/01/2026 5:16:20 AM
Action
Type
Old Value
New Value
Added
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.