Skip to main content
VulnerabilityPublished

CVE-2026-34538: Apache Airflow · Resource Exposure

Affects Apache AirflowSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.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 9 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade Apache Airflow to 3.2.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache AirflowAffected
  • >=3.0.0 <3.2.0
Fixed in
  • 3.2.0
PyPIapache-airflowpkg:pypi/apache-airflowOther threatsAffected
  • =3.0.0
Fixed in–

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.2.0 or later, where this issue is resolved. Until upgraded, restrict access to DAG Runs carefully to minimize exposure. Patch status is not explicitly confirmed in the advisory, but the vendor recommends upgrading to 3.2.0 for remediation.

Description

Apache Airflow versions 3.0.0 through 3.1.8 have a vulnerability where the DagRun wait endpoint returns XCom result values to users with only DAG Run read permissions, such as those assigned the Viewer role. This behavior violates the intended role-based access control (RBAC) model, which treats XCom as a separate protected resource and defines the Viewer role as read-only without access to sensitive execution results. The issue is resolved in Apache Airflow 3.2.0.

References

Community reviews

Loading reviews…