# Apache Airflow's \`/assets/events\` API returned asset events for every Dag in the deployment, with no filter restricting them to the Dags the caller is authorized to read. Any authenticated user hol...

Advisory record · `PYSEC-2026-3988`

- **Identifiers:** `PYSEC-2026-3988` · `BIT-airflow-2026-75158` · `CVE-2026-75158`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 21 Sept 2026
- **Updated:** 26 Sept 2026
- **Reviewed by a person:** No

Published by OSV at 21 Sept 2026, 15:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow` (PyPI): affected `<3.3.2`; fixed in `3.3.2`

## Machine-written summary

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

> Apache Airflow versions before 3.3.2 are affected: the /assets/events API returned asset events for all Dags with no filter by the caller's Dag-level read permissions. An authenticated user with asset-read access can see event details, including source Dag ID, task ID, run ID and timestamps, for Dags they should not be able to read, and the total count and pagination reveal that hidden Dags exist. Upgrade to apache-airflow 3.3.2 or later; no workaround is listed.

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

- 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.0064, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 21 Sept 2026, 14:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-75158)
- 21 Sept 2026, 15:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-75158)
- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3988)

## Sources

- [OSV: PYSEC-2026-3988](https://osv.dev/vulnerability/PYSEC-2026-3988)
- <http://www.openwall.com/lists/oss-security/2026/09/21/3>
- <https://lists.apache.org/thread/rx5lg86l0qkjl2s7dtmpqxjq0xplr4fy>

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/PYSEC-2026-3988>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-3988/>. Everything for agents: <https://agentprime.io/llms.txt>.