Loading story…
Apache disclosed two low-severity code execution issues in Apache Airflow tied to its XCom mechanism and addressed them in Airflow 3.2.0. CVE-2026-33858 affects Airflow versions 3.1.8 before 3.2.0 and stems from unsafe deserialization in the XCom API, where legacy serialization keys __type and __var can bypass protections and let a DAG author craft payloads that execute arbitrary code in the webserver context. Apache said the flaw was rated low severity because DAG authors are already treated as highly trusted users.
Apache also disclosed CVE-2025-54550, a low-severity remote code execution issue involving the documented example_xcom DAG pattern. The vulnerable pattern read XCom values in a way that could allow a UI user with permission to modify XComs to trigger arbitrary code execution on a worker through a race condition. Apache said official releases were not directly affected because example DAGs are not meant to be enabled in production, but organizations that copied the documented approach could reproduce the weakness in their own deployments; updated documentation in Airflow 3.2.0 provides a safer example.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
Apache publicly disclosed CVE-2026-30898 on the oss-sec mailing list, describing a low-severity issue in Airflow documentation that showed how to pass dag_run.conf into BashOperator in a way that could enable shell injection. Apache said Airflow versions before 3.2.0 were affected if users copied the example into their own DAGs, and advised reviewing deployments for adoption of the unsafe pattern.
Apache publicly disclosed CVE-2025-54550 on the oss-sec mailing list, describing a low-severity remote code execution issue caused by a race condition in the documented example_xcom DAG pattern. Apache noted that Airflow 3.2.0 documentation includes a more resilient example and credited Vincent55 Yang for reporting the issue.
Before Airflow 3.2.0, Apache Airflow documentation included an example_xcom DAG pattern that could allow arbitrary code execution on a worker via a race condition if a UI user with permission to modify XComs abused it. Apache said official releases were not affected because example DAGs are not meant to be enabled in production, but users who copied the pattern into their own deployments could reproduce the issue.
Apache publicly disclosed CVE-2026-33858 on the oss-sec mailing list, describing it as a low-severity unsafe deserialization vulnerability in Apache Airflow and recommending upgrade to version 3.2.0. The advisory credited wooseokdotkim for finding the issue and Amogh Desai for the remediation work.
Apache addressed CVE-2026-33858 in Airflow 3.2.0, fixing an unsafe deserialization flaw in the XCom API where legacy serialization keys (__type/__var) could bypass protections and let DAG authors trigger arbitrary code execution in the webserver context. The issue affected Airflow versions 3.1.8 before 3.2.0.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourceseclists.org
Open sourceseclists.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
German authorities issued advisories for **Apache Airflow** covering a vulnerability that can bypass security measures and a separate notice for **multiple vulnerabilities** affecting the workflow orchestration platform. The alerts indicate that Airflow deployments may be exposed to weaknesses that undermine intended protections and introduce additional security risk across affected environments. Organizations using Apache Airflow should review the referenced advisories, identify affected versions, and prioritize vendor-recommended updates or mitigations. Because Airflow is commonly used to manage automated data pipelines and scheduled jobs, successful exploitation could weaken access controls or expose connected systems and workflows to further compromise.
Jun 29, 2026
Apache disclosed two JWT-related vulnerabilities in Apache Airflow affecting versions `3.0.0` before `3.2.0`. The first, `CVE-2025-57735`, is a low-severity flaw in which logout did not invalidate authentication JWTs, leaving intercepted tokens usable after a user signed out. The second, `CVE-2026-31987`, is a moderate-severity issue that caused task JWTs to appear in logs, potentially exposing credentials to users who could then act as DAG authors. Apache said both issues are fixed in Airflow `3.2.0`, which adds token invalidation on logout and removes the logging exposure. Organizations running affected releases have been advised to upgrade to `3.2.0` or later, particularly where shared log access or concerns about token reuse could increase the risk of unauthorized access and privilege escalation.
Jun 29, 2026
German authorities published advisories for **multiple vulnerabilities** affecting both **Apache HTTP Server** and **Apache Airflow** components, expanding the list of enterprise Apache software requiring review. One notice, `dCERT Advisory 2026-1331`, covers several flaws in Apache HTTP Server, a widely deployed web server used in internet-facing and internal application environments. A separate notice, `dCERT Advisory 2026-1636`, reports multiple vulnerabilities in **Apache Airflow** provider packages, specifically the **Google** and **FAB** providers. While the advisories provided no public synopsis in the referenced notices, the disclosures indicate that organizations using these Apache products should identify affected deployments, review vendor guidance, and prioritize patching or other mitigations for exposed systems and workflow orchestration environments.
Jun 29, 2026