CVE-2026-22922VulnerabilityPublished 9 Feb 2026

CVE-2026-22922: Apache Airflow · Incorrect Use of Privileged APIs

Affects Apache AirflowSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.1.7 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.1.7

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache Airflow to 3.1.7.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Airflow	Affected >=3.1.0 <3.1.7	Fixed in 3.1.7

AI-suggested

The primary mitigation is to upgrade Apache Airflow installations to version 3.1.7 or later, where this authorization flaw is corrected. Organizations should implement a strict patch management process to ensure timely updates of workflow orchestration tools. Additionally, review and audit user permissions and roles within Airflow to enforce the principle of least privilege, ensuring users only have access necessary for their tasks. Implement monitoring and alerting on unusual access patterns to task logs, especially from users with limited permissions. Consider network segmentation and access controls to restrict Airflow UI and API access to trusted users and systems. If upgrading immediately is not feasible, temporarily restrict access to task logs or disable task log viewing features for users with custom limited permissions. Conduct regular security assessments and penetration testing focused on workflow management platforms to detect authorization weaknesses early.

Description

CVE-2026-22922 is an authorization vulnerability in Apache Airflow versions 3.1.0 through 3.1.6 that allows authenticated users with limited custom permissions to access task logs without proper authorization. This flaw arises from incorrect use of privileged APIs, classified under CWE-648. The vulnerability has a CVSS score of 6.5, indicating medium severity, with high impact on confidentiality but no impact on integrity or availability. Exploitation requires authentication but no user interaction, and the flaw is resolved in Apache Airflow 3.1.

Impact

For European organizations, the primary impact of CVE-2026-22922 is unauthorized disclosure of sensitive task log information. Task logs can contain detailed execution data, error messages, environment variables, and sometimes credentials or tokens used during workflow execution. Exposure of such information can lead to further attacks, including credential theft, reconnaissance, or exploitation of other vulnerabilities. Sectors heavily reliant on data pipelines and workflow automation—such as finance, telecommunications, manufacturing, and technology—may face increased risk if attackers gain access to internal operational data. The breach of confidentiality could also lead to regulatory compliance issues under GDPR if personal or sensitive data is exposed. Although the vulnerability does not affect system integrity or availability, the potential for information leakage can undermine trust and operational security. European organizations with multi-tenant or shared environments are particularly at risk if users with limited permissions can escalate visibility beyond intended boundaries.

CWE-648Incorrect Use of Privileged APIs (opens in a new tab)
Base weaknessLikelihood of exploit: Low
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
Implementation
Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
Architecture and Design
Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.
Implementation
If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Cross Site Tracing (opens in a new tab)
Hijacking a privileged process (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Feb 2026, 13:23 UTC

WeaknessesCWE-648

Technical details

References

Community reviews

Related threats