Before apache-airflow 3.3.0, a user authorized to read one Dag could disclose the source of other Dags co-located in the same source file. GET /api/v2/dagSources/{dag_id} — and the equivalent Dag-source view in the UI — returned the entire source file without redacting Dags the caller was not authorized to read, bypassing per-DAG read authorization. Deployments that co-locate multiple Dags in a single file and rely on per-DAG access control to limit source visibility are affected; single-Dag-per-file deployments are not. Upgrade to apache-airflow 3.3.0 or later.
CVE-2026-49296
Score 6.5 from GitHub Security Advisory published 2026-07-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EPSS
- 44.6%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 8, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026oss-security - CVE-2026-49296: Apache Airflow: Per-DAG read bypass discloses co-located DAGs' source via GET /api/v2/dagSources/{dag_id}
http://www.openwall.com/lists/oss-security/2026/07/07/5Apply per-file authorization to dag-source endpoint
Fix merged in apache/airflow PR #67662 on 2026-06-05 — awaiting tagged release
https://github.com/apache/airflow/pull/67662Vendor Advisories for CVE-2026-49296(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 11:34 UTCEG score recompute
- 2026-07-12 11:34 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 13:06 UTCEG score recompute
- 2026-07-11 13:05 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 14:37 UTCEG score recompute▲ 6.50
- 2026-07-10 14:37 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:53 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:06 UTCMITRE cvelistV5
- 2026-07-07 11:56 UTCNVD update
- 2026-07-07 10:07 UTCEG score recompute
- 2026-07-07 10:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-49296?
When was CVE-2026-49296 disclosed?
Is CVE-2026-49296 actively exploited?
What is the CVSS score of CVE-2026-49296?
How do I remediate CVE-2026-49296?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-49296
Is Your Infrastructure Affected by CVE-2026-49296?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.