PYSEC-2026-3994
Vulnerability from pysec - Published: 2026-08-12 16:17 - Updated: 2026-09-28 09:39Apache Airflow's asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom result check on wait_dag_run_until_finished authorized the target Dag without its team, unlike every other authorization site. A team-aware auth manager distinguishes a team-scoped Dag from a global one by that field -- the Keycloak auth manager, for example, checks the DAG resource instead of DAG:<team> -- so the team-scoped permission that should gate the request was never consulted. In a deployment running multi-team mode with a team-aware auth manager, an authenticated user in one team could trigger Dag runs belonging to another team, supplying their own dag_run_id and conf, and could read another team's XCom values. Deployments using the FAB auth manager are unaffected, as it has no multi-team support. Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag's team at both sites.
| Name | purl | apache-airflow | pkg:pypi/apache-airflow |
|---|
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "apache-airflow",
"purl": "pkg:pypi/apache-airflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.3.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.10.0",
"1.10.1",
"1.10.10",
"1.10.10rc1",
"1.10.10rc2",
"1.10.10rc3",
"1.10.10rc4",
"1.10.10rc5",
"1.10.11",
"1.10.11rc1",
"1.10.11rc2",
"1.10.12",
"1.10.12rc1",
"1.10.12rc2",
"1.10.12rc3",
"1.10.12rc4",
"1.10.13",
"1.10.13rc1",
"1.10.14",
"1.10.14rc1",
"1.10.14rc2",
"1.10.14rc3",
"1.10.14rc4",
"1.10.15",
"1.10.15rc1",
"1.10.1b1",
"1.10.1rc2",
"1.10.2",
"1.10.2b2",
"1.10.2rc1",
"1.10.2rc2",
"1.10.2rc3",
"1.10.3",
"1.10.3b1",
"1.10.3b2",
"1.10.3rc1",
"1.10.3rc2",
"1.10.4",
"1.10.4b2",
"1.10.4rc1",
"1.10.4rc2",
"1.10.4rc3",
"1.10.4rc4",
"1.10.4rc5",
"1.10.5",
"1.10.5rc1",
"1.10.6",
"1.10.6rc1",
"1.10.6rc2",
"1.10.7",
"1.10.7rc1",
"1.10.7rc2",
"1.10.7rc3",
"1.10.8",
"1.10.8rc1",
"1.10.9",
"1.10.9rc1",
"1.8.1",
"1.8.2",
"1.8.2rc1",
"1.9.0",
"2.0.0",
"2.0.0b1",
"2.0.0b2",
"2.0.0b3",
"2.0.0rc1",
"2.0.0rc2",
"2.0.0rc3",
"2.0.1",
"2.0.1rc1",
"2.0.1rc2",
"2.0.2",
"2.0.2rc1",
"2.1.0",
"2.1.0rc1",
"2.1.0rc2",
"2.1.1",
"2.1.1rc1",
"2.1.2",
"2.1.2rc1",
"2.1.3",
"2.1.3rc1",
"2.1.4",
"2.1.4rc1",
"2.1.4rc2",
"2.10.0",
"2.10.0b1",
"2.10.0b2",
"2.10.0rc1",
"2.10.1",
"2.10.1rc1",
"2.10.2",
"2.10.2rc1",
"2.10.3",
"2.10.3rc1",
"2.10.3rc2",
"2.10.4",
"2.10.4rc1",
"2.10.5",
"2.10.5rc1",
"2.11.0",
"2.11.0rc1",
"2.11.1",
"2.11.1rc1",
"2.11.1rc2",
"2.11.2",
"2.11.2rc1",
"2.2.0",
"2.2.0b1",
"2.2.0b2",
"2.2.0rc1",
"2.2.1",
"2.2.1rc1",
"2.2.1rc2",
"2.2.2",
"2.2.2rc1",
"2.2.2rc2",
"2.2.3",
"2.2.3rc1",
"2.2.3rc2",
"2.2.4",
"2.2.4rc1",
"2.2.5",
"2.2.5rc1",
"2.2.5rc2",
"2.2.5rc3",
"2.3.0",
"2.3.0b1",
"2.3.0rc1",
"2.3.0rc2",
"2.3.1",
"2.3.1rc1",
"2.3.2",
"2.3.2rc1",
"2.3.2rc2",
"2.3.3",
"2.3.3rc1",
"2.3.3rc2",
"2.3.3rc3",
"2.3.4",
"2.3.4rc1",
"2.4.0",
"2.4.0b1",
"2.4.0rc1",
"2.4.1",
"2.4.1rc1",
"2.4.2",
"2.4.2rc1",
"2.4.3",
"2.4.3rc1",
"2.5.0",
"2.5.0rc1",
"2.5.0rc2",
"2.5.0rc3",
"2.5.1",
"2.5.1rc1",
"2.5.1rc2",
"2.5.2",
"2.5.2rc1",
"2.5.2rc2",
"2.5.3",
"2.5.3rc1",
"2.5.3rc2",
"2.6.0",
"2.6.0b1",
"2.6.0rc1",
"2.6.0rc2",
"2.6.0rc3",
"2.6.0rc4",
"2.6.0rc5",
"2.6.1",
"2.6.1rc1",
"2.6.1rc2",
"2.6.1rc3",
"2.6.2",
"2.6.2rc1",
"2.6.2rc2",
"2.6.3",
"2.6.3rc1",
"2.7.0",
"2.7.0b1",
"2.7.0rc1",
"2.7.0rc2",
"2.7.1",
"2.7.1rc1",
"2.7.1rc2",
"2.7.2",
"2.7.2rc1",
"2.7.3",
"2.7.3rc1",
"2.8.0",
"2.8.0b1",
"2.8.0rc1",
"2.8.0rc2",
"2.8.0rc3",
"2.8.0rc4",
"2.8.1",
"2.8.1rc1",
"2.8.2",
"2.8.2rc1",
"2.8.2rc2",
"2.8.2rc3",
"2.8.3",
"2.8.3rc1",
"2.8.4",
"2.8.4rc1",
"2.9.0",
"2.9.0b1",
"2.9.0b2",
"2.9.0rc1",
"2.9.0rc2",
"2.9.0rc3",
"2.9.1",
"2.9.1rc1",
"2.9.1rc2",
"2.9.2",
"2.9.2rc1",
"2.9.3",
"2.9.3rc1",
"3.0.0",
"3.0.0b4",
"3.0.0rc1",
"3.0.0rc1.post1",
"3.0.0rc1.post2",
"3.0.0rc1.post3",
"3.0.0rc1.post4",
"3.0.0rc2",
"3.0.0rc3",
"3.0.0rc4",
"3.0.1",
"3.0.1rc1",
"3.0.2",
"3.0.2rc1",
"3.0.2rc2",
"3.0.3",
"3.0.3rc1",
"3.0.3rc2",
"3.0.3rc3",
"3.0.3rc4",
"3.0.3rc5",
"3.0.3rc6",
"3.0.4",
"3.0.4rc1",
"3.0.4rc2",
"3.0.5",
"3.0.5rc1",
"3.0.5rc2",
"3.0.5rc3",
"3.0.6",
"3.0.6rc1",
"3.0.6rc2",
"3.1.0",
"3.1.0b1",
"3.1.0b2",
"3.1.0rc1",
"3.1.0rc2",
"3.1.1",
"3.1.1rc1",
"3.1.1rc2",
"3.1.2",
"3.1.2rc1",
"3.1.2rc2",
"3.1.3",
"3.1.3rc1",
"3.1.4",
"3.1.4rc1",
"3.1.4rc2",
"3.1.5",
"3.1.5rc1",
"3.1.6",
"3.1.6rc1",
"3.1.7",
"3.1.7rc1",
"3.1.7rc2",
"3.1.8",
"3.1.8rc1",
"3.1.8rc2",
"3.2.0",
"3.2.0b1",
"3.2.0b2",
"3.2.0rc1",
"3.2.0rc2",
"3.2.1",
"3.2.1rc1",
"3.2.1rc2",
"3.2.1rc3",
"3.2.2",
"3.2.2rc1",
"3.2.2rc2",
"3.2.2rc3",
"3.3.0",
"3.3.0b1",
"3.3.0b2",
"3.3.0rc1",
"3.3.0rc2",
"3.3.1rc1",
"3.3.1rc2"
]
}
],
"aliases": [
"CVE-2026-68971"
],
"details": "Apache Airflow\u0027s asset materialization endpoint (`POST /api/v2/assets/{asset_id}/materialize`) and the XCom result check on `wait_dag_run_until_finished` authorized the target Dag without its team, unlike every other authorization site. A team-aware auth manager distinguishes a team-scoped Dag from a global one by that field -- the Keycloak auth manager, for example, checks the `DAG` resource instead of `DAG:\u003cteam\u003e` -- so the team-scoped permission that should gate the request was never consulted. In a deployment running multi-team mode with a team-aware auth manager, an authenticated user in one team could trigger Dag runs belonging to another team, supplying their own `dag_run_id` and `conf`, and could read another team\u0027s XCom values. Deployments using the FAB auth manager are unaffected, as it has no multi-team support. Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag\u0027s team at both sites.",
"id": "PYSEC-2026-3994",
"modified": "2026-09-28T09:39:33.945844Z",
"published": "2026-08-12T16:17:19.970Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/apache/airflow/pull/70893"
},
{
"type": "ARTICLE",
"url": "http://www.openwall.com/lists/oss-security/2026/08/12/15"
},
{
"type": "ARTICLE",
"url": "https://lists.apache.org/thread/kfxqqwgojdjdnt6bxg3ord4y41y334fo"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.