# Apache Airflow has an authorization bypass in DagRun wait endpoint

Advisory record · `GHSA-r7vr-m4jw-r794`

- **Identifiers:** `GHSA-r7vr-m4jw-r794` · `BIT-airflow-2026-34538` · `CVE-2026-34538` · `PYSEC-2026-21`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-668](https://cwe.mitre.org/data/definitions/668.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 9 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Apr 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow` (PyPI): affected `>=3.0.0, <3.2.0`; fixed in `3.2.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Airflow versions 3.0.0 through 3.1.x (before 3.2.0) expose XCom result values through the DagRun wait endpoint. A user with only DAG Run read permissions, such as the Viewer role, can see these values, even though XCom is meant to be a separately protected resource. Upgrade apache-airflow to 3.2.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0070, the 53rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 Apr 2026, 09:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-34538)
- 9 Apr 2026, 10:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-34538)
- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r7vr-m4jw-r794)

## Sources

- [GitHub Advisory Database: GHSA-r7vr-m4jw-r794](https://github.com/advisories/GHSA-r7vr-m4jw-r794)
- [OSV: GHSA-r7vr-m4jw-r794](https://osv.dev/vulnerability/GHSA-r7vr-m4jw-r794)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34538>
- <https://github.com/apache/airflow/pull/64415>
- <https://github.com/apache/airflow>
- <https://github.com/apache/airflow/releases/tag/3.2.0>
- <https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2026-21.yaml>
- <https://lists.apache.org/thread/9mq3msqhmgjwdzbr6bgthj4brb3oz9fl>
- <http://www.openwall.com/lists/oss-security/2026/04/09/9>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r7vr-m4jw-r794>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r7vr-m4jw-r794/>. Everything for agents: <https://agentprime.io/llms.txt>.
