cve.bz

CVE-2026-49296 apache airflow

6.5 mediumEPSS 0.6%Fix available

Medium (6.5) in apache airflow. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow 3.3.0.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-49296 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49296?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49296?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49296 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-49296

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-49296](https://cve.bz/cve/badge/CVE-2026-49296.svg)](https://cve.bz/cve/CVE-2026-49296)

HTML:

<a href="https://cve.bz/cve/CVE-2026-49296"><img src="https://cve.bz/cve/badge/CVE-2026-49296.svg" alt="CVE-2026-49296"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4fh7-7jx4-8f6cPyPIapache-airflow<3.3.03.3.0
PYSEC-2026-2083PyPIapache-airflow<3.3.03.3.0

References

Check your stackJSON