CVE-2025-54550 (GCVE-0-2025-54550)

Vulnerability from cvelistv5 – Published: 2026-04-15 00:22 – Updated: 2026-04-15 03:03
VLAI?
Title
Apache Airflow: RCE by race condition in example_xcom dag
Summary
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.
Severity ?
No CVSS data available.
CWE
  • CWE-94 - Improper Control of Generation of Code ('Code Injection')
Assigner
Impacted products
Vendor Product Version
Apache Software Foundation Apache Airflow Affected: 0 , < 3.2.0 (semver)
Create a notification for this product.
Credits
Vincent55 Yang
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-04-15T03:03:33.178Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/04/15/1"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://pypi.python.org",
          "defaultStatus": "unaffected",
          "packageName": "apache-airflow",
          "product": "Apache Airflow",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "3.2.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Vincent55 Yang"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe example \u003ccode\u003eexample_xcom\u003c/code\u003e\u0026nbsp;that was included in airflow documentation implemented unsafe pattern of reading value\u003cbr\u003efrom xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary\u003cbr\u003eexecution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability.\u003c/p\u003e\u003cp\u003eIt does not affect Airflow release - example_dags are not supposed to be enabled in production environment, however\u003cbr\u003eusers following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of\u003cbr\u003ethe example with improved resiliance for that case.\u003c/p\u003eUsers who followed that pattern are advised to adjust their implementations accordingly.\u003cbr\u003e\u003cbr\u003e"
            }
          ],
          "value": "The example example_xcom\u00a0that was included in airflow documentation implemented unsafe pattern of reading value\nfrom xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary\nexecution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability.\n\nIt does not affect Airflow release - example_dags are not supposed to be enabled in production environment, however\nusers following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of\nthe example with improved resiliance for that case.\n\nUsers who followed that pattern are advised to adjust their implementations accordingly."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "Low"
            },
            "type": "Textual description of severity"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-94",
              "description": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-15T00:22:03.305Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/3mf4cfx070ofsnf9qy0s2v5gqb5sc2g1"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/apache/airflow/pull/63200"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Apache Airflow: RCE by race condition in example_xcom dag",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2025-54550",
    "datePublished": "2026-04-15T00:22:03.305Z",
    "dateReserved": "2025-07-24T21:10:16.628Z",
    "dateUpdated": "2026-04-15T03:03:33.178Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-54550",
      "date": "2026-04-15",
      "epss": "0.00026",
      "percentile": "0.07269"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-54550\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2026-04-15T04:17:32.670\",\"lastModified\":\"2026-04-15T04:17:32.670\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The example example_xcom\u00a0that was included in airflow documentation implemented unsafe pattern of reading value\\nfrom xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary\\nexecution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability.\\n\\nIt does not affect Airflow release - example_dags are not supposed to be enabled in production environment, however\\nusers following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of\\nthe example with improved resiliance for that case.\\n\\nUsers who followed that pattern are advised to adjust their implementations accordingly.\"}],\"metrics\":{},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-94\"}]}],\"references\":[{\"url\":\"https://github.com/apache/airflow/pull/63200\",\"source\":\"security@apache.org\"},{\"url\":\"https://lists.apache.org/thread/3mf4cfx070ofsnf9qy0s2v5gqb5sc2g1\",\"source\":\"security@apache.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2026/04/15/1\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…