CVE-2025-66236

{"id": "CVE-2025-66236", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-66236", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-04-15T19:20:26.164642Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache Airflow", "versions": [{"status": "affected", "version": "3.0.0", "lessThan": "3.2.0", "versionType": "semver"}], "packageName": "apache-airflow", "collectionURL": "https://pypi.python.org", "defaultStatus": "unaffected"}]}], "published": "2026-04-13T15:17:05.953", "references": [{"url": "https://github.com/apache/airflow/pull/58662", "tags": ["Issue Tracking"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread/g8fyy1tkmxkkfk7tx2v6h8mvwzpyykbo", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2026/04/13/6", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "Before Airflow 3.2.0, it was unclear that secure Airflow deployments require the Deployment Manager to take appropriate actions and pay attention to security details and security model of Airflow. Some assumptions the Deployment Manager could make were not clear or explicit enough, even though Airflow's intentions and security model of Airflow did not suggest different assumptions. The overall security model [1], workload isolation [2], and JWT authentication details [3] are now described in more detail. Users concerned with role isolation and following the Airflow security model of Airflow are advised to upgrade to Airflow 3.2, where several security improvements have been implemented. They should also read and follow the relevant documents to make sure that their deployment is secure enough. It also clarifies that the Deployment Manager is ultimately responsible for securing your Airflow deployment. This had also been communicated via Airflow 3.2.0 Blog announcement [4].\n\n[1] Security Model: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html \n[2] Workload isolation: https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html \n[3] JWT Token authentication: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html \n[4] Airflow 3.2.0 Blog announcement: https://airflow.apache.org/blog/airflow-3.2.0/ \n\n\n\nUsers are recommended to upgrade to version 3.2.0, which fixes this issue."}, {"lang": "es", "value": "Antes de Airflow 3.2.0, no estaba claro que las implementaciones seguras de Airflow requieren que el Gestor de Implementaci\u00f3n tome las acciones apropiadas y preste atenci\u00f3n a los detalles de seguridad y al modelo de seguridad de Airflow. Algunas suposiciones que el Gestor de Implementaci\u00f3n podr\u00eda hacer no eran lo suficientemente claras o expl\u00edcitas, a pesar de que las intenciones de Airflow y el modelo de seguridad de Airflow no suger\u00edan suposiciones diferentes. El modelo de seguridad general [1], el aislamiento de la carga de trabajo [2] y los detalles de autenticaci\u00f3n JWT [3] ahora se describen con m\u00e1s detalle. Se aconseja a los usuarios preocupados por el aislamiento de roles y por seguir el modelo de seguridad de Airflow que actualicen a Airflow 3.2, donde se han implementado varias mejoras de seguridad. Tambi\u00e9n deben leer y seguir los documentos relevantes para asegurarse de que su implementaci\u00f3n sea lo suficientemente segura. Tambi\u00e9n aclara que el Gestor de Implementaci\u00f3n es, en \u00faltima instancia, responsable de asegurar su implementaci\u00f3n de Airflow. Esto tambi\u00e9n se hab\u00eda comunicado a trav\u00e9s del anuncio del blog de Airflow 3.2.0 [4].\n\n[1] Modelo de Seguridad: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\n[2] Aislamiento de la carga de trabajo: https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html\n[3] Autenticaci\u00f3n de tokens JWT: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\n[4] Anuncio del blog de Airflow 3.2.0: https://airflow.apache.org/blog/airflow-3.2.0/\n\nSe recomienda a los usuarios actualizar a la versi\u00f3n 3.2.0, que soluciona este problema."}], "lastModified": "2026-10-07T09:10:00.160", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D8133DE3-F556-42F5-8298-FD4CF40787B6", "versionEndExcluding": "3.2.0", "versionStartIncluding": "3.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}