Cyber Resilience

CVE-2026-22922

Apache Airflow 3.1.0 – 3.1.7

Published
09 February 2026
Modified
11 February 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0038 31th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2026-22922 is a medium-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Apache Airflow. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Abuse Elevation Control Mechanism (T1548); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Apache Airflow versions 3.1.0 through 3.1.6 contain an authorization flaw that can allow an authenticated user with custom permissions limited to task access to view task logs without having task log access. Users are recommended to upgrade to Apache Airflow…

more

3.1.7 or later, which resolves this issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-25754Same product: Apache Airflow
CVE-2021-38540Same product: Apache Airflow
CVE-2026-38743Same product: Apache Airflow
CVE-2026-40690Same product: Apache Airflow
CVE-2023-50944Same product: Apache Airflow
CVE-2024-27906Same product: Apache Airflow
CVE-2026-30911Same product: Apache Airflow
CVE-2026-41014Same product: Apache Airflow
CVE-2026-40963Same product: Apache Airflow
CVE-2026-32228Same product: Apache Airflow

Affected Assets

apache
airflow
3.1.0 — 3.1.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.

Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.

Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.

Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect incorrect privileged API calls but does not prevent them at design time.

degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

prevents

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

prevents

Application security requirements can specify correct invocation of privileged APIs.

prevents

Secure architecture principles guide proper privilege separation and API usage.

References