# In Apache Airflow, prior to version 2.4.1, deactivating a user wouldn't prevent an already authenticated user from being able to continue using the UI or API.

Advisory record · `GHSA-3q8r-f3pj-3gc4`

- **Identifiers:** `GHSA-3q8r-f3pj-3gc4` · `BIT-airflow-2022-41672` · `CVE-2022-41672` · `PYSEC-2022-42983`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 7 Oct 2022
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Oct 2022, 07:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## Machine-written summary

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

> Apache Airflow versions before 2.4.2rc1 are affected. An already authenticated user whose account has been deactivated can keep using the web UI and API, because deactivation does not end their existing session. Upgrade apache-airflow to 2.4.2rc1 or later. The source gives few details beyond this and does not list a workaround.

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

No source has published a CVSS score for this record yet.

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

## Timeline

This record came from the full history of the GitHub Advisory Database, published 7 Oct 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-3q8r-f3pj-3gc4](https://github.com/advisories/GHSA-3q8r-f3pj-3gc4)
- [OSV: GHSA-3q8r-f3pj-3gc4](https://osv.dev/vulnerability/GHSA-3q8r-f3pj-3gc4)
- <https://github.com/apache/airflow/pull/26635>
- <https://github.com/apache/airflow/pull/26635>
- <https://lists.apache.org/thread/ohf3pvd3dftb8zb01yngbn1jtkq5m08y>
- <https://lists.apache.org/thread/ohf3pvd3dftb8zb01yngbn1jtkq5m08y>
- <https://github.com/advisories/GHSA-3q8r-f3pj-3gc4>

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-3q8r-f3pj-3gc4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3q8r-f3pj-3gc4/>. Everything for agents: <https://agentprime.io/llms.txt>.
