# The partitioned_dag_runs endpoints in the Airflow UI enforced only asset-level access control, not per-Dag authorization. An authenticated UI/API user with global Asset:read permission could enumer...

Advisory record · `GHSA-x2x7-p37c-43cr`

- **Identifiers:** `GHSA-x2x7-p37c-43cr` · `BIT-airflow-2026-41014` · `CVE-2026-41014` · `PYSEC-2026-182`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 1 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Jun 2026, 09:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## Machine-written summary

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

> The apache-airflow package, versions 3.2.0 before 3.2.2, has a flaw in the partitioned_dag_runs endpoints of the Airflow UI, which checked only asset-level access and not per-Dag authorization. An authenticated user with global Asset:read permission could view partition run state, schedule configuration, and asset wiring for Dags they should not be able to read. Upgrade to apache-airflow 3.2.2 or later.

Written 5 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

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 30th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 Jun 2026, 07:53 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-41014)
- 1 Jun 2026, 09:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-41014)
- 31 Oct 2026, 14:43 UTC: First seen by agentprime
- 31 Oct 2026, 14:43 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-182)

## Sources

- [GitHub Advisory Database: GHSA-x2x7-p37c-43cr](https://github.com/advisories/GHSA-x2x7-p37c-43cr)
- [OSV: GHSA-x2x7-p37c-43cr](https://osv.dev/vulnerability/GHSA-x2x7-p37c-43cr)
- <http://www.openwall.com/lists/oss-security/2026/05/31/4>
- <https://lists.apache.org/thread/12nbzwwby7g883w2j13gn7ny1545xob9>
- <https://github.com/apache/airflow/pull/65344>
- <https://github.com/advisories/GHSA-x2x7-p37c-43cr>

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-x2x7-p37c-43cr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x2x7-p37c-43cr/>. Everything for agents: <https://agentprime.io/llms.txt>.
