Information Exposure Through Log Files Affecting airflow-3-advanced-compat package, versions <3.2.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Information Exposure Through Log Files vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-MINIMOSLATEST-AIRFLOW3ADVANCEDCOMPAT-16087419
- published16 Apr 2026
- disclosed13 Apr 2026
Introduced: 13 Apr 2026
NewCVE-2025-66236 (opens in a new tab)How to fix?
Upgrade Minimos:latest airflow-3-advanced-compat to version 3.2.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream airflow-3-advanced-compat package and not the airflow-3-advanced-compat package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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].
[1] Security Model: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [2] Workload isolation: https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html [3] JWT Token authentication: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [4] Airflow 3.2.0 Blog announcement: https://airflow.apache.org/blog/airflow-3.2.0/
Users are recommended to upgrade to version 3.2.0, which fixes this issue.
References
- https://www.cve.org/CVERecord?id=CVE-2025-66236
- https://github.com/advisories/GHSA-j86x-fwp2-qh7v
- https://osv.dev/vulnerability/MINI-96f7-92gv-vjph
- https://osv.dev/vulnerability/CVE-2025-66236
- https://github.com/apache/airflow/pull/58662
- https://lists.apache.org/thread/g8fyy1tkmxkkfk7tx2v6h8mvwzpyykbo
- http://www.openwall.com/lists/oss-security/2026/04/13/6