Vulnerability database · updated every 15 minutes
New vulnerabilities in the software websites run.
CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.
- Tracked
- 55,370
- Published in 7 days
- 1,871
- Critical in 30 days
- 488
- Actively exploited
- 542
Results for “Apache Airflow”
176 vulnerabilities- High 7.3
CVE-2026-45360 · Apache Airflow
Apache Airflow: Arbitrary import in custom deadline-reference deserialization
Published 1 Jun 2026 · Fixed in 3.0.0, 3.2.2 · NVD, CVE Program - Low 3.1
CVE-2026-45426 · Apache Airflow
Apache Airflow: Log server JWT authorization bypass via Python lstrip() character stripping allows cross-Dag log access
Published 1 Jun 2026 · Fixed in 3.2.2 · NVD, CVE Program - Medium 4.3
CVE-2026-46764 · Apache Airflow
Apache Airflow: Event Log detail endpoint bypasses DAG-scoped event log permission filter
Published 1 Jun 2026 · Fixed in 3.0.0, 3.2.2 · NVD, CVE Program - Medium 6.5
CVE-2026-48726 · Apache Airflow
Apache Airflow: revoke_token() unreachable in FabAuthManager / KeycloakAuthManager logout path
Published 1 Jun 2026 · Fixed in 3.0.0, 3.2.2 · NVD, CVE Program - High 8.8
CVE-2026-49298 · Apache Airflow
Apache Airflow: JWT Token Exposure in KubernetesExecutor Command-Line Arguments
Published 1 Jun 2026 · Fixed in 3.0.0, 3.2.2 · NVD, CVE Program - Medium 6.5
CVE-2026-45192 · Apache Airflow
Apache Airflow: Incomplete Redaction of Sensitive Fields in Connection Extra API Response
Published 1 Jun 2026 · Fixed in 3.0.0, 3.2.2 · NVD, CVE Program - Medium 5.9
CVE-2026-41016 · Apache Airflow
Apache Airflow's SMTP provider `SmtpHook` called Python's `smtplib.SMTP.starttls()` without an SSL context, so no certificate validation was performed on the TLS upgrade. A man-in-the-middle between the Airflow worker and the SMTP server could present a self-signed certificate, complete the STARTTLS upgrade, and capture the SMTP credentials sent during the subsequent `login()` call. Users are…
Published 30 Apr 2026 · Fixed in 3.0.0 · NVD - Medium 4.3
CVE-2026-40690 · Apache Airflow
The asset dependency graph did not restrict nodes by the viewer's DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope. Users are recommended to upgrade to version 3.2.1, which fixes this issue.
Published 24 Apr 2026 · Fixed in 3.2.1 · NVD - Medium 4.3
CVE-2026-38743 · Apache Airflow
The authenticated /ui/dags endpoint did not enforce per-DAG access control on embedded Human-in-the-Loop (HITL) and TaskInstance records: a logged-in Airflow user with read access to at least one DAG could retrieve HITL prompts (including their request parameters) and full TaskInstance details for DAGs outside their authorized scope. Because HITL prompts and TaskInstance fields routinely carry…
Published 24 Apr 2026 · Fixed in 3.2.1 · NVD - Low 3.7
CVE-2026-32690 · Apache Airflow
Secrets in Variables saved as JSON dictionaries were not properly redacted - in case thee variables were retrieved by the user the secrets stored as nested fields were not masked. If you do not store variables with sensitive values in JSON form, you are not affected. Otherwise please upgrade to Apache Airflow 3.2.0 that has the fix implemented
Published 18 Apr 2026 · Fixed in 3.2.0 · NVD - High 7.5
CVE-2026-32228 · Apache Airflow
UI / API User with asset materialize permission could trigger dags they had no access to. Users are advised to migrate to Airflow version 3.2.0 that fixes the issue.
Published 18 Apr 2026 · Fixed in 3.2.0 · NVD - High 7.5
CVE-2026-30912 · Apache Airflow
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.
Published 18 Apr 2026 · Fixed in 3.2.0 · NVD - High 8.8
CVE-2026-30898 · Apache Airflow
An example of BashOperator in Airflow documentation suggested a way of passing dag_run.conf in the way that could cause unsanitized user input to be used to escalate privileges of UI user to allow execute code on worker. Users should review if any of their own DAGs have adopted this incorrect advice.
Published 18 Apr 2026 · Fixed in 3.2.0 · NVD - High 7.2
CVE-2026-25917 · Apache Airflow
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.
Published 18 Apr 2026 · Fixed in 3.2.0 · NVD - High 7.5
CVE-2026-31987 · Apache Airflow
JWT Tokens used by tasks were exposed in logs. This could allow UI users to act as Dag Authors. Users are advised to upgrade to Airflow version that contains fix. Users are recommended to upgrade to version 3.2.0, which fixes this issue.
Published 16 Apr 2026 · Fixed in 3.2.0 · NVD - Medium 6.5
CVE-2026-25219 · Apache Airflow
The `access_key` and `connection_string` connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be…
Published 15 Apr 2026 · Fixed in 3.2.0 · NVD - High 8.1
CVE-2025-54550 · Apache Airflow
The example example_xcom that was included in airflow documentation implemented unsafe pattern of reading value from xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary execution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability. It does not affect Airflow release - example_dags are…
Published 15 Apr 2026 · Fixed in 3.2.0 · NVD - High 8.8
CVE-2026-33858 · Apache Airflow
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 resolves this issue.
Published 13 Apr 2026 · Fixed in 3.2.0 · NVD - High 7.5
CVE-2025-66236 · Apache Airflow
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…
Published 13 Apr 2026 · Fixed in 3.2.0 · NVD - Critical 9.1
CVE-2025-57735 · Apache Airflow
When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+ Users are recommended to…
Published 9 Apr 2026 · Fixed in 3.2.0 · NVD - Medium 6.5
CVE-2026-34538 · Apache Airflow
Apache Airflow versions 3.0.0 through 3.1.8 DagRun wait endpoint returns XCom result values even to users who only have DAG Run read permissions, such as the Viewer role.This behavior conflicts with the FAB RBAC model, which treats XCom as a separate protected resource, and with the security model documentation that defines the Viewer role as read-only. Airflow uses the FAB Auth Manager to…
Published 9 Apr 2026 · Fixed in 3.2.0 · NVD - High 8.1
CVE-2026-30911 · Apache Airflow
Apache Airflow versions 3.1.0 through 3.1.7 missing authorization vulnerability in the Execution API's Human-in-the-Loop (HITL) endpoints that allows any authenticated task instance to read, approve, or reject HITL workflows belonging to any other task instance. Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.
Published 17 Mar 2026 · Fixed in 3.1.8 · NVD - High 7.5
CVE-2026-28779 · Apache Airflow
Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url. This allows any application co-hosted under the same domain to capture valid Airflow session tokens from HTTP request headers, allowing full session takeover without attacking Airflow itself. Users are recommended to upgrade to Apache…
Published 17 Mar 2026 · Fixed in 3.1.8 · NVD - Medium 4.3
CVE-2026-28563 · Apache Airflow
Apache Airflow versions 3.1.0 through 3.1.7 /ui/dependencies endpoint returns the full DAG dependency graph without filtering by authorized DAG IDs. This allows an authenticated user with only DAG Dependencies permission to enumerate DAGs they are not authorized to view. Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.
Published 17 Mar 2026 · Fixed in 3.1.8 · NVD - Medium 6.5
CVE-2026-26929 · Apache Airflow
Apache Airflow versions 3.0.0 through 3.1.7 FastAPI DagVersion listing API does not apply per-DAG authorization filtering when the request is made with dag_id set to "~" (wildcard for all DAGs). As a result, version metadata of DAGs that the requester is not authorized to access is returned. Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.
Published 17 Mar 2026 · Fixed in 3.1.8 · NVD - Medium 6.5
CVE-2025-27555 · Apache Airflow
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,…
Published 24 Feb 2026 · Fixed in 2.11.1 · NVD - High 8.4
CVE-2024-56373 · Apache Airflow
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…
Published 24 Feb 2026 · Fixed in 2.11.1 · NVD - Medium 6.5
CVE-2025-65995 · Apache Airflow
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.4 and 2.11.1, and users are strongly advised to upgrade to prevent…
Published 21 Feb 2026 · Fixed in 2.11.1, 3.1.4 · NVD - Medium 6.5
CVE-2026-24098 · Apache Airflow
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
Published 9 Feb 2026 · Fixed in 3.1.7 · NVD - Medium 6.5
CVE-2026-22922 · Apache Airflow
Apache Airflow versions 3.1.0 through 3.1.6 contain an authorization flaw that can allow an authenticated user with custom permissions limited to task access to view task logs without having task log access. Users are recommended to upgrade to Apache Airflow 3.1.7 or later, which resolves this issue.
Published 9 Feb 2026 · Fixed in 3.1.7 · NVD - High 7.5
CVE-2025-68675 · Apache Airflow
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…
Published 16 Jan 2026 · Fixed in 3.1.6 · NVD - High 7.5
CVE-2025-68438 · Apache Airflow
In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation…
Published 16 Jan 2026 · Fixed in 3.1.6 · NVD - Medium 6.5
CVE-2025-66388 · Apache Airflow
A vulnerability in Apache Airflow allowed authenticated UI users to view secret values in rendered templates due to secrets not being properly redacted, potentially exposing secrets to users without the appropriate authorization. Users are recommended to upgrade to version 3.1.4, which fixes this issue.
Published 15 Dec 2025 · Fixed in 3.1.4 · NVD - Medium 4.6
CVE-2025-62503 · Apache Airflow
User with CREATE and no UPDATE privilege for Pools, Connections, Variables could update existing records via bulk create API with overwrite action.
Published 30 Oct 2025 · Fixed in 3.1.1 · NVD - Medium 5.4
CVE-2025-62402 · Apache Airflow
API users via `/api/v2/dagReports` could perform Dag code execution in the context of the api-server if the api-server was deployed in the environment where Dag files were available.
Published 30 Oct 2025 · Fixed in 3.1.1 · NVD - Medium 4.6
CVE-2025-54941 · Apache Airflow
An example dag `example_dag_decorator` had non-validated parameter that allowed the UI user to redirect the example to a malicious server and execute code on worker. This however required that the example dags are enabled in production (not default) or the example dag code copied to build your own similar dag. If you used the `example_dag_decorator` please review it and apply the changes…
Published 30 Oct 2025 · Fixed in 3.0.5 · NVD - Medium 6.5
CVE-2025-54831 · Apache Airflow
Apache Airflow 3 introduced a change to the handling of sensitive information in Connections. The intent was to restrict access to sensitive connection fields to Connection Editing Users, effectively applying a "write-only" model for sensitive values. In Airflow 3.0.3, this model was unintentionally violated: sensitive connection information could be viewed by users with READ permissions through…
Published 26 Sept 2025 · NVD - High 7.5
CVE-2024-45784 · Apache Airflow
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.…
Published 15 Nov 2024 · Fixed in 2.10.3 · NVD - Medium 4.9
CVE-2024-50378 · Apache Airflow
Airflow versions before 2.10.3 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 variables 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…
Published 8 Nov 2024 · Fixed in 2.10.3 · NVD - High 8.8
CVE-2024-45498 · Apache Airflow
Example DAG: example_inlet_event_extra.py shipped with Apache Airflow version 2.10.0 has a vulnerability that allows an authenticated attacker with only DAG trigger permission to execute arbitrary commands. If you used that example as the base of your DAGs - please review if you have not copied the dangerous example; see https://github.com/apache/airflow/pull/41873 for more information. We…
Published 7 Sept 2024 · NVD - High 8.8
CVE-2024-45034 · Apache Airflow
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.
Published 7 Sept 2024 · Fixed in 2.10.1 · NVD - Medium 6.1
CVE-2024-41937 · Apache Airflow
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.
Published 21 Aug 2024 · Fixed in 2.10.0 · NVD - High 8.8
CVE-2024-39877 · Apache Airflow
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.
Published 17 Jul 2024 · Fixed in 2.9.3 · NVD - Medium 5.4
CVE-2024-39863 · Apache Airflow
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.
Published 17 Jul 2024 · Fixed in 2.9.3 · NVD - Medium 5.5
CVE-2024-25142 · Apache Airflow
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.
Published 14 Jun 2024 · Fixed in 2.9.2 · NVD - Medium 5.4
CVE-2024-32077 · Apache Airflow
Apache Airflow version 2.9.0 has a vulnerability that allows an authenticated attacker to inject malicious data into the task instance logs. Users are recommended to upgrade to version 2.9.1, which fixes this issue.
Published 14 May 2024 · NVD - Medium 4.3
CVE-2024-31869 · Apache Airflow
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…
Published 18 Apr 2024 · Fixed in 2.9.0 · NVD - Medium 5.3
CVE-2024-29735 · Apache Airflow
Improper Preservation of Permissions vulnerability in Apache Airflow.This issue affects Apache Airflow from 2.8.2 through 2.8.3. Airflow's local file task handler in Airflow incorrectly set permissions for all parent folders of log folder, in default configuration adding write access to Unix group of the folders. In the case Airflow is run with the root user (not recommended) it added group…
Published 26 Mar 2024 · NVD - High 8.1
CVE-2024-28746 · Apache Airflow
Apache Airflow, versions 2.8.0 through 2.8.2, has a vulnerability that allows an authenticated user with limited permissions to access resources such as variables, connections, etc from the UI which they do not have permission to access. Users of Apache Airflow are recommended to upgrade to version 2.8.3 or newer to mitigate the risk associated with this vulnerability
Published 14 Mar 2024 · Fixed in 2.8.3 · NVD - Medium 4.7
CVE-2024-26280 · Apache Airflow
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…
Published 1 Mar 2024 · Fixed in 2.8.2 · NVD
Where it comes from
The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.
- NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
- OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
- WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
- Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
- The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
- CISA's Known Exploited Vulnerabilities catalog.
Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.
Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.