CVE-2026-49296 Apache Software Foundation CVE debrief

Who should care

Deployments that co-locate multiple Dags in a single file and rely on per-DAG access control to limit source visibility are affected by CVE-2026-49296; single-Dag-per-file deployments are not. Operators, platform administrators, vulnerability management teams, and security teams should review their configurations and plan for mitigations.

Technical summary

CVE-2026-49296 is a vulnerability in apache-airflow that allows a user authorized to read one Dag to disclose the source of other Dags co-located in the same source file. The vulnerability exists in versions before 3.3.0 and is due to the `GET /api/v2/dagSources/{dag_id}` endpoint and the equivalent Dag-source view in the UI returning the entire source file without redacting Dags the caller was not authorized to read, bypassing per-DAG read authorization. Affected deployments should upgrade to apache-airflow 3.3.0 or later and review access controls.

Defensive priority

CVE-2026-49296 has a medium to high defensive priority due to the potential for sensitive information disclosure. Defenders should prioritize reviewing access controls, monitoring Dag sources, and planning for upgrades or mitigations.

Recommended defensive actions

• Upgrade to apache-airflow 3.3.0 or later
• Review and adjust per-DAG access control to limit source visibility
• Monitor and restrict access to Dag sources
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record was published on 2026-07-07T10:16:41.603Z and has not been modified since then. The NVD entry is currently Received. The vulnerability exists in apache-airflow versions before 3.3.0. Deployments should verify their configurations and review access controls for Dag sources.

Official resources