Database/Control plane, storage & DevOps
Apache Airflow: pre-3.2 deployments lack the isolation guarantees operators assumed, per clarified security model
Impact
Apache Airflow before 3.2.0 did not provide the role and workload isolation that many deployment managers assumed it did; the project has now documented the actual security model, the workload isolation boundary and the JWT token authentication details explicitly, and shipped isolation improvements in 3.2.0. The record scores this as a confidentiality issue reachable over the network without authentication (C:H/I:N/A:N) but does not describe a single concrete code flaw, so treat it as a deployment-posture advisory rather than an exploit. It matters on a GPU fleet because Airflow is commonly the thing that submits training and batch inference jobs: a DAG author who is not supposed to be a cluster admin may in practice reach credentials or task context belonging to other teams' pipelines, and those credentials are the ones that hold GPU queues, object storage and model registries. Nothing here is specific to a GPU node - the exposure is in the orchestrator.
Who can reach it
Anyone who can author or modify a DAG, plus anyone who can reach the Airflow API or task execution interface with a token issued by the deployment. Whether authentication is required depends on how the deployment is configured, which is precisely the point of the advisory; the CVSS vector in the record assumes an unauthenticated network attacker.
What to do
Upgrade to Airflow 3.2.0 and then read and apply the now-explicit security model, workload isolation and JWT token authentication documents - the upgrade alone is not the whole fix, because the deployment manager is responsible for configuring the isolation. For most operators this is a scheduler, API server and worker restart on the control-plane hosts; GPU nodes running the resulting jobs do not need to be drained. Expect configuration review work alongside the version bump.
References
Related entries
- Apache Airflow: oversized rendered template fields bypass user-registered secret masksCVE-2025-68438 · Apache Airflow (Rendered Templates UI, secrets masker)High
- Apache Airflow: proxy URLs with embedded credentials are not masked in task logsCVE-2025-68675 · Apache Airflow (Connection proxy fields, log masking)High
- GitLab CE/EE: unauthenticated poisoning of the cached OIDC discovery document redirects auth flowsCVE-2026-112212 · GitLab CE/EE (cached OAuth/OIDC discovery document)High
- GitLab EE: unauthenticated crafted file upload can deny service to the instanceCVE-2026-1184 · GitLab EE (file upload handling)High
- IBM Storage Scale GUI (hardcoded inter-node token): A hardcoded token in the Storage Scale GUI source, usedCVE-2026-13460 · IBM Storage Scale GUI (hardcoded inter-node token)High
- Performance Co-Pilot: signed integer overflow in __pmGetPDU permanently blinds the collector daemonCVE-2026-16529 · Performance Co-Pilot pmcd/PMAPI (__pmGetPDU PDU length handling)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.