CVE-2025-66236

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2025-66236", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2025-11-25T16:03:35.709Z", "datePublished": "2026-04-13T14:20:37.180Z", "dateUpdated": "2026-11-03T06:51:04.950Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-11-03T06:51:04.950Z"}, "title": "Apache Airflow: Secrets from Airflow config file logged in plain text in DAG run logs UI", "problemTypes": [{"descriptions": [{"description": "CWE-532: Insertion of Sensitive Information into Log File", "lang": "en", "cweId": "CWE-532", "type": "CWE"}]}], "source": {"discovery": "UNKNOWN"}, "affected": [{"vendor": "Apache Software Foundation", "product": "Apache Airflow", "collectionURL": "https://pypi.python.org", "packageName": "apache-airflow-core", "versions": [{"status": "affected", "version": "3.0.0", "lessThan": "3.2.0", "versionType": "semver"}], "defaultStatus": "unaffected", "packageURL": "pkg:pypi/apache-airflow-core"}], "descriptions": [{"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": "en", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<p>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].</p><blockquote><p>[1] Security Model: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html</a><br>[2] Workload isolation: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html</a><br>[3] JWT Token authentication: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html</a><br>[4] Airflow 3.2.0 Blog announcement: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/blog/airflow-3.2.0/\">https://airflow.apache.org/blog/airflow-3.2.0/</a></p></blockquote><br><br>Users are recommended to upgrade to version 3.2.0, which fixes this issue."}]}], "references": [{"url": "https://github.com/apache/airflow/pull/58662", "tags": ["patch"]}, {"url": "https://lists.apache.org/thread/g8fyy1tkmxkkfk7tx2v6h8mvwzpyykbo", "tags": ["vendor-advisory"]}], "metrics": [{"other": {"type": "Textual description of severity", "content": {"text": "moderate"}}}], "credits": [{"lang": "en", "value": "Saurabh Banawar", "type": "finder"}, {"lang": "en", "value": "Amogh Desai", "type": "remediation developer"}], "x_generator": {"engine": "Vulnogram 0.2.0"}}, "adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/04/13/6"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-04-13T16:26:55.846Z"}}, {"metrics": [{"cvssV3_1": {"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"}}, {"other": {"type": "ssvc", "content": {"timestamp": "2026-04-15T19:20:26.164642Z", "id": "CVE-2025-66236", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-04-15T20:03:37.134Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/04/13/6"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-04-13T16:26:55.846Z"}}, {"title": "CISA ADP Vulnrichment", "metrics": [{"cvssV3_1": {"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"}}, {"other": {"type": "ssvc", "content": {"id": "CVE-2025-66236", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-04-15T19:20:26.164642Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-04-15T19:19:59.721Z"}}], "cna": {"title": "Apache Airflow: Secrets from Airflow config file logged in plain text in DAG run logs UI", "source": {"discovery": "UNKNOWN"}, "credits": [{"lang": "en", "type": "finder", "value": "Saurabh Banawar"}, {"lang": "en", "type": "remediation developer", "value": "Amogh Desai"}], "metrics": [{"other": {"type": "Textual description of severity", "content": {"text": "moderate"}}}], "affected": [{"vendor": "Apache Software Foundation", "product": "Apache Airflow", "versions": [{"status": "affected", "version": "3.0.0", "lessThan": "3.2.0", "versionType": "semver"}], "packageURL": "pkg:pypi/apache-airflow-core", "packageName": "apache-airflow-core", "collectionURL": "https://pypi.python.org", "defaultStatus": "unaffected"}], "references": [{"url": "https://github.com/apache/airflow/pull/58662", "tags": ["patch"]}, {"url": "https://lists.apache.org/thread/g8fyy1tkmxkkfk7tx2v6h8mvwzpyykbo", "tags": ["vendor-advisory"]}], "x_generator": {"engine": "Vulnogram 0.2.0"}, "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.", "supportingMedia": [{"type": "text/html", "value": "<p>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].</p><blockquote><p>[1] Security Model: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html</a><br>[2] Workload isolation: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html</a><br>[3] JWT Token authentication: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html\">https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html</a><br>[4] Airflow 3.2.0 Blog announcement: <a target=\"_blank\" rel=\"nofollow\" href=\"https://airflow.apache.org/blog/airflow-3.2.0/\">https://airflow.apache.org/blog/airflow-3.2.0/</a></p></blockquote><br><br>Users are recommended to upgrade to version 3.2.0, which fixes this issue.", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-532", "description": "CWE-532: Insertion of Sensitive Information into Log File"}]}], "providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-11-03T06:51:04.950Z"}}}, "cveMetadata": {"cveId": "CVE-2025-66236", "state": "PUBLISHED", "dateUpdated": "2026-11-03T06:51:04.950Z", "dateReserved": "2025-11-25T16:03:35.709Z", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "datePublished": "2026-04-13T14:20:37.180Z", "assignerShortName": "apache"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"collectionURL": "https://pypi.python.org", "defaultStatus": "unaffected", "packageName": "apache-airflow-core", "packageURL": "pkg:pypi/apache-airflow-core", "product": "Apache Airflow", "vendor": "Apache Software Foundation", "versions": [{"lessThan": "3.2.0", "status": "affected", "version": "3.0.0", "versionType": "semver"}]}], "source": "security@apache.org"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*", "matchCriteriaId": "D8133DE3-F556-42F5-8298-FD4CF40787B6", "versionEndExcluding": "3.2.0", "versionStartIncluding": "3.0.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "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."}], "id": "CVE-2025-66236", "lastModified": "2026-11-03T07:17:51.993", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-66236", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-04-15T19:20:26.164642Z", "version": "2.0.3"}}]}, "published": "2026-04-13T15:17:05.953", "references": [{"source": "security@apache.org", "tags": ["Issue Tracking"], "url": "https://github.com/apache/airflow/pull/58662"}, {"source": "security@apache.org", "tags": ["Mailing List", "Vendor Advisory"], "url": "https://lists.apache.org/thread/g8fyy1tkmxkkfk7tx2v6h8mvwzpyykbo"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Mailing List", "Third Party Advisory"], "url": "http://www.openwall.com/lists/oss-security/2026/04/13/6"}], "sourceIdentifier": "security@apache.org", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-532"}], "source": "security@apache.org", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[3.0.0,3.2.0)"}}], "enrichment": {"confidence": 95.0, "confidence_source": "inferred", "scores": [{"score": 95.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Apache Airflow", "source": "cna", "vendor": "Apache Software Foundation"}, "product": "airflow", "vendor": "apache"}], "analysis": {"en": {"generated_at": "2026-04-15T22:28:52.423393+00:00", "value": {"mitigation_remediation": ["Upgrade Apache Airflow to version 3.2.0 or later.", "Follow the updated security model and workload isolation guidelines as described in the Airflow documentation.", "Rotate any credentials that may have been logged before the upgrade.", "Restrict DAG run log visibility in the Airflow UI to users with legitimate need, following the principle of least privilege."], "summary": {"action": "Immediate Upgrade", "impact": "Confidential Information Disclosure"}, "threat_synthesis": {"affected_systems": "Apache Airflow from the Apache Software Foundation is affected. All releases earlier than version 3.2.0 are impacted because the fix was introduced in that release; no later sub\u2011versions are mentioned.", "description_and_impact": "The vulnerability permits secrets from the Airflow configuration file to be logged in plain text within DAG run logs shown in the Airflow web UI. An attacker who can view these logs could recover sensitive credentials, potentially enabling further compromise of the underlying infrastructure. This causes a confidentiality breach of configuration data and is categorized as CWE\u2011532. Based on the description, it is inferred that any user with permission to view DAG run logs can see the secrets; the specific attack vector is not explicitly stated but log access appears to be the primary path.", "risk_and_exploitability": "The CVSS score is 7.5, indicating a high severity. EPSS is < 1%, suggesting a low probability of widespread exploitation, and the vulnerability is not listed in CISA KEV. The exposure of credentials remains a serious confidentiality breach. The likely exploitation path is through authorized UI access to DAG run logs, inferred from log exposure in the UI. No public exploits are known, but logged secrets could be leveraged once an adversary gains or cannot restrict log visibility."}}}}, "created": "2026-04-14T16:19:10.867674+00:00", "updated": "2026-04-15T22:30:16.082813+00:00", "vendors": ["apache", "apache$PRODUCT$airflow"]}