Search for packages
| purl | pkg:pypi/apache-airflow@2.7.3 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1azm-hsvr-f3e8
Aliases: CVE-2023-25693 GHSA-j69x-v4wc-3fpf PYSEC-2023-314 |
Improper Input Validation vulnerability in the Apache Airflow Sqoop Provider. This issue affects Apache Airflow Sqoop Provider versions before 3.1.1. |
Affected by 15 other vulnerabilities. |
|
VCID-4u8d-ezsr-sqcz
Aliases: BIT-airflow-2023-50943 CVE-2023-50943 GHSA-c3c6-f2ww-xfr2 PYSEC-2024-13 |
Apache Airflow, versions before 2.8.1, have a vulnerability that allows a potential attacker to poison the XCom data by bypassing the protection of "enable_xcom_pickling=False" configuration setting resulting in poisoned data after XCom deserialization. This vulnerability is considered low since it requires a DAG author to exploit it. Users are recommended to upgrade to version 2.8.1 or later, which fixes this issue. |
Affected by 21 other vulnerabilities. Affected by 19 other vulnerabilities. |
|
VCID-5ppv-384x-ekeb
Aliases: CVE-2025-27555 GHSA-8r55-rv5w-6pfm |
Apache Airflow exposes sensitive information in its log files Airflow versions before 2.11.1 have a vulnerability that allows authenticated users with audit log access to see sensitive values in audit logs which they should not see. When sensitive connection parameters were set via airflow CLI, values of those variables appeared in the audit log and were stored unencrypted in the Airflow database. While this risk is limited to users with audit log access, it is recommended to upgrade to Airflow 2.11.1 or a later version, which addresses this issue. Users who previously used the CLI to set connections should manually delete entries with those connection sensitive values from the log table. This is similar but not the same issue as CVE-2024-50378 |
Affected by 4 other vulnerabilities. |
|
VCID-82p8-yujf-hkdd
Aliases: BIT-airflow-2023-50944 CVE-2023-50944 GHSA-vm5m-qmrx-fw8w PYSEC-2024-14 |
Apache Airflow, versions before 2.8.1, have a vulnerability that allows an authenticated user to access the source code of a DAG to which they don't have access. This vulnerability is considered low since it requires an authenticated user to exploit it. Users are recommended to upgrade to version 2.8.1, which fixes this issue. |
Affected by 21 other vulnerabilities. Affected by 19 other vulnerabilities. |
|
VCID-8htr-89h8-6fba
Aliases: CVE-2024-50378 GHSA-j857-2pwm-jjmm |
Affected by 8 other vulnerabilities. |
|
|
VCID-8m3p-yzr8-yyhj
Aliases: BIT-airflow-2024-41937 CVE-2024-41937 GHSA-w7cp-g8v7-r54m PYSEC-2024-181 |
Apache Airflow, versions before 2.10.0, have a vulnerability that allows the developer of a malicious provider to execute a cross-site scripting attack when clicking on a provider documentation link. This would require the provider to be installed on the web server and the user to click the provider link. Users should upgrade to 2.10.0 or later, which fixes this vulnerability. |
Affected by 12 other vulnerabilities. |
|
VCID-8tgv-2cpd-xyh9
Aliases: CVE-2024-56373 GHSA-r837-hpv7-pc2f |
Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table DAG Author (who already has quite a lot of permissions) could manipulate database of Airflow 2 in the way to execute arbitrary code in the web-server context, which they should normally not be able to do, leading to potentially remote code execution in the context of web-server (server-side) as a result of a user viewing historical task information. The functionality responsible for that (log template history) has been disabled by default in 2.11.1 and users should upgrade to Airflow 3 if they want to continue to use log template history. They can also manually modify historical log file names if they want to see historical logs that were generated before the last log template change. |
Affected by 4 other vulnerabilities. |
|
VCID-arbk-dryb-qkda
Aliases: BIT-airflow-2024-26280 CVE-2024-26280 GHSA-6xwf-xvf3-v459 PYSEC-2024-42 |
Apache Airflow, versions before 2.8.2, has a vulnerability that allows authenticated Ops and Viewers users to view all information on audit logs, including dag names and usernames they were not permitted to view. With 2.8.2 and newer, Ops and Viewer users do not have audit log permission by default, they need to be explicitly granted permissions to see the logs. Only admin users have audit log permission by default. Users of Apache Airflow are recommended to upgrade to version 2.8.2 or newer to mitigate the risk associated with this vulnerability |
Affected by 18 other vulnerabilities. |
|
VCID-cxqa-pqca-pqgc
Aliases: BIT-airflow-2023-47265 CVE-2023-47265 GHSA-pxch-wr7m-rwxj PYSEC-2023-264 |
Apache Airflow, versions 2.6.0 through 2.7.3 has a stored XSS vulnerability that allows a DAG author to add an unbounded and not-sanitized javascript in the parameter description field of the DAG. This Javascript can be executed on the client side of any of the user who looks at the tasks in the browser sandbox. While this issue does not allow to exit the browser sandbox or manipulation of the server-side data - more than the DAG author already has, it allows to modify what the user looking at the DAG details sees in the browser - which opens up all kinds of possibilities of misleading other users. Users of Apache Airflow are recommended to upgrade to version 2.8.0 or newer to mitigate the risk associated with this vulnerability |
Affected by 23 other vulnerabilities. |
|
VCID-g9j4-fhpm-uuba
Aliases: CVE-2024-31869 GHSA-2522-mrjc-m688 |
Apache Airflow: Sensitive configuration for providers displayed when "non-sensitive-only" config used Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the "configuration" UI page when "non-sensitive-only" was set as "webserver.expose_config" configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your "expose_config" configuration to False as a workaround. This is similar, but different to CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq which concerned API, not UI configuration page. |
Affected by 16 other vulnerabilities. |
|
VCID-hpf3-3z3m-6ydt
Aliases: BIT-airflow-2024-25142 CVE-2024-25142 GHSA-9xpj-62mm-24h2 PYSEC-2024-195 |
Use of Web Browser Cache Containing Sensitive Information vulnerability in Apache Airflow. Airflow did not return "Cache-Control" header for dynamic content, which in case of some browsers could result in potentially storing sensitive data in local cache of the browser. This issue affects Apache Airflow: before 2.9.2. Users are recommended to upgrade to version 2.9.2, which fixes the issue. |
Affected by 14 other vulnerabilities. |
|
VCID-huhh-68py-hbe2
Aliases: CVE-2025-65995 GHSA-gfw7-2v73-69wg |
Apache Airflow error reporting may expose full kwargs When a DAG failed during parsing, Airflow’s error-reporting in the UI could include the full kwargs passed to the operators. If those kwargs contained sensitive values (such as secrets), they might be exposed in the UI tracebacks to authenticated users who had permission to view that DAG. The issue has been fixed in Airflow 3.1.5rc1 and 2.11.1, and users are strongly advised to upgrade to prevent potential disclosure of sensitive information. |
Affected by 4 other vulnerabilities. Affected by 14 other vulnerabilities. |
|
VCID-j6uh-kx6m-sydp
Aliases: BIT-airflow-2026-25917 CVE-2026-25917 GHSA-6ffj-2wg2-w45j PYSEC-2026-13 |
Dag Authors, who normally should not be able to execute code in the webserver context could craft XCom payload causing the webserver to execute arbitrary code. Since Dag Authors are already highly trusted, severity of this issue is Low. Users are recommended to upgrade to Apache Airflow 3.2.0, which fixes the issue. |
Affected by 0 other vulnerabilities. |
|
VCID-kb4a-mm13-63bj
Aliases: BIT-airflow-2024-45784 CVE-2024-45784 GHSA-46c3-5xc5-wwhv PYSEC-2024-182 |
Apache Airflow versions before 2.10.3 contain a vulnerability that could expose sensitive configuration variables in task logs. This vulnerability allows DAG authors to unintentionally or intentionally log sensitive configuration variables. Unauthorized users could access these logs, potentially exposing critical data that could be exploited to compromise the security of the Airflow deployment. In version 2.10.3, secrets are now masked in task logs to prevent sensitive configuration variables from being exposed in the logging output. Users should upgrade to Airflow 2.10.3 or the latest version to eliminate this vulnerability. If you suspect that DAG authors could have logged the secret values to the logs and that your logs are not additionally protected, it is also recommended that you update those secrets. |
Affected by 8 other vulnerabilities. |
|
VCID-mbgq-fq5n-kufh
Aliases: BIT-airflow-2024-39877 CVE-2024-39877 GHSA-g5hv-r743-v8pm PYSEC-2024-190 |
Apache Airflow 2.4.0, and versions before 2.9.3, has a vulnerability that allows authenticated DAG authors to craft a doc_md parameter in a way that could execute arbitrary code in the scheduler context, which should be forbidden according to the Airflow Security model. Users should upgrade to version 2.9.3 or later which has removed the vulnerability. |
Affected by 12 other vulnerabilities. |
|
VCID-nfbc-tutd-37bw
Aliases: BIT-airflow-2023-50783 CVE-2023-50783 GHSA-5938-79hg-xh3q PYSEC-2023-267 |
Apache Airflow, versions before 2.8.0, is affected by a vulnerability that allows an authenticated user without the variable edit permission, to update a variable. This flaw compromises the integrity of variable management, potentially leading to unauthorized data modification. Users are recommended to upgrade to 2.8.0, which fixes this issue |
Affected by 21 other vulnerabilities. |
|
VCID-rysu-xhvt-yqda
Aliases: BIT-airflow-2023-48291 CVE-2023-48291 GHSA-8f57-wcmg-4jmh PYSEC-2023-265 |
Apache Airflow, in versions prior to 2.8.0, contains a security vulnerability that allows an authenticated user with limited access to some DAGs, to craft a request that could give the user write access to various DAG resources for DAGs that the user had no access to, thus, enabling the user to clear DAGs they shouldn't. This is a missing fix for CVE-2023-42792 in Apache Airflow 2.7.2Â Users of Apache Airflow are strongly advised to upgrade to version 2.8.0 or newer to mitigate the risk associated with this vulnerability. |
Affected by 21 other vulnerabilities. |
|
VCID-tpjn-4kru-vucv
Aliases: BIT-airflow-2026-30912 CVE-2026-30912 GHSA-w7cf-2pmc-5m4c PYSEC-2026-18 |
In case of SQL errors, exception/stack trace of errors was exposed in API even if "api/expose_stack_traces" was set to false. That could lead to exposing additional information to potential attacker. Users are recommended to upgrade to Apache Airflow 3.2.0, which fixes the issue. |
Affected by 0 other vulnerabilities. |
|
VCID-unq1-wwfg-6ydk
Aliases: BIT-airflow-2023-49920 CVE-2023-49920 GHSA-6m9r-7wrx-xmr6 PYSEC-2023-266 |
Apache Airflow, version 2.7.0 through 2.7.3, has a vulnerability that allows an attacker to trigger a DAG in a GET request without CSRF validation. As a result, it was possible for a malicious website opened in the same browser - by the user who also had Airflow UI opened - to trigger the execution of DAGs without the user's consent. Users are advised to upgrade to version 2.8.0 or later which is not affected |
Affected by 23 other vulnerabilities. Affected by 21 other vulnerabilities. |
|
VCID-vras-f42j-xqfg
Aliases: BIT-airflow-2025-68675 CVE-2025-68675 GHSA-7c2f-r6gc-h92h PYSEC-2026-10 |
In Apache Airflow versions before 3.1.6, and 2.11.1 the proxies and proxy fields within a Connection may include proxy URLs containing embedded authentication information. These fields were not treated as sensitive by default and therefore were not automatically masked in log output. As a result, when such connections are rendered or printed to logs, proxy credentials embedded in these fields could be exposed. Users are recommended to upgrade to 3.1.6 or later for Airflow 3, and 2.11.1 or later for Airflow 2 which fixes this issue |
Affected by 4 other vulnerabilities. Affected by 11 other vulnerabilities. |
|
VCID-vwv4-7y7y-9fcj
Aliases: BIT-airflow-2026-24098 CVE-2026-24098 GHSA-5g2w-9f8g-g5q7 PYSEC-2026-12 |
Apache Airflow versions 3.0.0 - 3.1.7, has vulnerability that allows authenticated UI users with permission to one or more specific Dags to view import errors generated by other Dags they did not have access to. Users are advised to upgrade to 3.1.7 or later, which resolves this issue |
Affected by 9 other vulnerabilities. |
|
VCID-w8ff-8479-rbfq
Aliases: BIT-airflow-2024-45034 CVE-2024-45034 GHSA-92xg-gmrq-5c3w PYSEC-2024-212 |
Apache Airflow versions before 2.10.1 have a vulnerability that allows DAG authors to add local settings to the DAG folder and get it executed by the scheduler, where the scheduler is not supposed to execute code submitted by the DAG author. Users are advised to upgrade to version 2.10.1 or later, which has fixed the vulnerability. |
Affected by 10 other vulnerabilities. |
|
VCID-xwza-guvs-83a9
Aliases: BIT-airflow-2024-39863 CVE-2024-39863 GHSA-j482-47xf-p25c PYSEC-2024-189 |
Apache Airflow versions before 2.9.3 have a vulnerability that allows an authenticated attacker to inject a malicious link when installing a provider. Users are recommended to upgrade to version 2.9.3, which fixes this issue. |
Affected by 12 other vulnerabilities. |
|
VCID-yrx8-dtav-83av
Aliases: BIT-airflow-2024-27906 CVE-2024-27906 GHSA-6v6w-h8m6-7mv2 PYSEC-2024-245 |
Apache Airflow, versions before 2.8.2, has a vulnerability that allows authenticated users to view DAG code and import errors of DAGs they do not have permission to view through the API and the UI. Users of Apache Airflow are recommended to upgrade to version 2.8.2 or newer to mitigate the risk associated with this vulnerability |
Affected by 18 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1963-1kyn-2ban | We failed to apply CVE-2023-40611 in 2.7.1 and this vulnerability was marked as fixed then. Apache Airflow, versions before 2.7.3, is affected by a vulnerability that allows authenticated and DAG-view authorized Users to modify some DAG run detail values when submitting notes. This could have them alter details such as configuration parameters, start date, etc. Users should upgrade to version 2.7.3 or later which has removed the vulnerability. |
BIT-airflow-2023-47037
CVE-2023-47037 GHSA-hm9r-7f84-25c9 PYSEC-2023-232 |
| VCID-fctg-457f-4uae | Apache Airflow, versions before 2.7.3, has a vulnerability that allows an authorized user who has access to read specific DAGs only, to read information about task instances in other DAGs. This is a different issue than CVE-2023-42663 but leading to similar outcome. Users of Apache Airflow are advised to upgrade to version 2.7.3 or newer to mitigate the risk associated with this vulnerability. |
BIT-airflow-2023-42781
CVE-2023-42781 GHSA-r7x6-xfcm-3mxv PYSEC-2023-231 |