cve.bz

CVE-2026-34538 apache airflow: Exposure of Resource to Wrong Sphere

6.5 mediumEPSS 0.7%Fix available

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

On this page
Apache Airflow versions 3.0.0 through 3.1.8 DagRun wait endpoint returns XCom result values even to users who only have DAG Run read permissions, such as the Viewer role.This behavior conflicts with the FAB RBAC model, which treats XCom as a separate protected resource, and with the security model documentation that defines the Viewer role as read-only. Airflow uses the FAB Auth Manager to manage access control on a per-resource basis. The Viewer role is intended to be read-only by default, and the security model documentation defines Viewer users as those who can inspect DAGs without accessing sensitive execution results. Users are recommended to upgrade to Apache Airflow 3.2.0 which resolves this issue.

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.7% (unchanged from 0.7% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th 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-04-09. 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-668 Exposure of Resource to Wrong Sphere
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-34538 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34538?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34538?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-34538 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-34538

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-34538](https://cve.bz/cve/badge/CVE-2026-34538.svg)](https://cve.bz/cve/CVE-2026-34538)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r7vr-m4jw-r794PyPIapache-airflow>=3.0.0 <3.2.03.2.0
PYSEC-2026-21PyPIapache-airflow>=3.0.0 <3.2.03.2.0

References

Check your stackJSON