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

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.

No CVSS scoreEPSS 0.015 · 74th percentile

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.

PackageEcosystemAffectedFixed in
apache-airflowPyPI<2.4.2rc12.4.2rc1
Identifiers
GHSA-3q8r-f3pj-3gc4 · BIT-airflow-2022-41672 · CVE-2022-41672 · PYSEC-2022-42983
Weakness (CWE)
CWE-613
Published
7 Oct 2022
Updated
10 Jun 2026

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

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.