Defined in 3 files
Last patched
_is_team_specific_accessed_as_global in apache/airflow was changed by 3 published CVE fixes in 2026, in 5 distinct patches that added or removed 108 lines in total.
The name occurs in 3 files: providers/microsoft/azure/src/airflow/providers/microsoft/azure/secrets/key_vault.py, airflow-core/src/airflow/secrets/environment_variables.py, providers/yandex/src/airflow/providers/yandex/secrets/lockbox.py.
apache/airflow has 200 CVEs with a located fix in total, so 2% of them touched this function.
Every published CVE whose fix changed _is_team_specific_accessed_as_global, newest first, with the lines each fix touched.
CVE-2026-68076 · airflow-core/src/airflow/secrets/environment_variables.py · lines 54–89 · +27 −5
CVE-2026-68871 · providers/yandex/src/airflow/providers/yandex/secrets/lockbox.py · lines 260–291 · +28 −3
CVE-2026-68870 · providers/microsoft/azure/src/airflow/providers/microsoft/azure/secrets/key_vault.py · lines 215–267 · +41 −4
Get an alert when the next CVE fix lands in apache/airflow, with the patched functions.
Monitor airflow CVEsFunctions in the same files that CVE fixes also changed.
Functions in apache/airflow changed by the most CVE fixes.
Common questions about CVE fixes to _is_team_specific_accessed_as_global.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
