VulnerabilityPublished 9 Feb 2026Updated 10 Mar 2026

CVE-2026-24098: Apache Airflow · Information Exposure

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 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.0.0 <3.1.7	Fixed in 3.1.7

AI-suggested

To mitigate CVE-2026-24098, organizations should promptly upgrade Apache Airflow to version 3.1.7 or later, where the vulnerability has been fixed. Beyond patching, administrators should review and enforce strict role-based access controls (RBAC) to limit user permissions to only those DAGs necessary for their role, minimizing the number of users who can access any DAGs. Monitoring and logging access to DAGs and error messages should be enhanced to detect anomalous or unauthorized access attempts. Consider implementing network segmentation and multi-factor authentication (MFA) for Airflow access to reduce the risk of compromised credentials being used to exploit this vulnerability. Additionally, review Airflow configurations to ensure error messages and logs do not expose sensitive information unnecessarily. Regular security assessments and audits of Airflow deployments can help identify and remediate similar information disclosure issues proactively.

Description

CVE-2026-24098 is a medium severity vulnerability in Apache Airflow versions 3.0.0 through 3.1.7 that allows authenticated users with access to specific DAGs to view import errors from other DAGs they are not authorized to access. This exposure of sensitive information could reveal internal system details or configuration errors, potentially aiding attackers in further exploitation. The vulnerability requires authenticated access but no user interaction beyond login. It impacts confidentiality but not integrity or availability. Organizations using affected Airflow versions should upgrade to 3.1.

Impact

The primary impact of CVE-2026-24098 is the unauthorized disclosure of sensitive information contained in import error messages from DAGs that an authenticated user should not access. This exposure can aid attackers or malicious insiders in understanding the internal workings, configurations, or vulnerabilities of the Airflow environment, potentially enabling privilege escalation, lateral movement, or targeted attacks against the infrastructure. While the vulnerability does not directly compromise data integrity or system availability, the confidentiality breach can undermine organizational security posture and compliance with data protection regulations. Organizations relying on Apache Airflow for critical workflow orchestration, especially those handling sensitive data or operating in regulated industries, face increased risk of information leakage and subsequent exploitation. The requirement for authentication limits the attack surface to insiders or compromised accounts, but given Airflow’s role in many enterprises, the risk remains significant. The absence of known exploits reduces immediate threat but does not eliminate future risk.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (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 17 Mar 2026, 19:31 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats