Skip to main content
VulnerabilityPublished Updated

CVE-2026-49296: Apache Airflow · Insecure Direct Object Reference

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.3.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.16.5
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Apache Airflow and apache-airflow-core to 3.3.0.

Affected software

ProductAffectedFixed in
Apache Airflowapache-airflow-coreAffected
  • >=3.0.0 <3.3.0
Fixed in
  • 3.3.0
PyPIapache-airflowpkg:pypi/apache-airflowOther threatsAffected
  • =3.0.0
Fixed in–
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • >=3.0.0 <3.3.0
Fixed in
  • 3.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Airflow to version 3.3.0 or later, where this vulnerability is fixed. Deployments using single-DAG-per-file layouts are not affected and do not require changes. Patch status is not explicitly confirmed beyond the recommendation to upgrade; check the vendor advisory for the latest remediation guidance.

Description

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.

References

Community reviews

Loading reviews…