Answer in brief
CVE-2025-54550 records a High severity (CVSS 8.1) vulnerability in Apache Airflow: RCE by race condition in example_xcom dag. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/Apache Airflow (generic), Apache Software Foundation/apache-airflow-core (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/Apache Airflow (generic), Apache Software Foundation/apache-airflow-core (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/apache-airflowgeneric | >=0 <3.2.0 | 3.2.0 |
| Apache Software Foundation/apache-airflowgeneric | >=0 <3.0.0 | 3.0.0 |
| Apache Software Foundation/Apache Airflowgeneric | >=0 <3.2.0 | 3.2.0 |
| Apache Software Foundation/apache-airflow-coregeneric | >=3.0.0 <3.2.0 | 3.2.0 |
| apache-airflowpip | <3.2.0 | 3.2.0 |
Published upstream
Apr 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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 not supposed to be enabled in production environment, however users following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of the example with improved resiliance for that case. Users who followed that pattern are advised to adjust their implementations accordingly.
Quoted source text, attributed separately from HOL analysis.