VulnerabilityPublished 1 Jun 2026

CVE-2026-42360: Apache Airflow · Information Exposure

Affects Apache AirflowSource CVE Database V5

Compare

Mentioned vulnerabilities

CVE-2025-68438

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

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.5Medium

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

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

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 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 and apache-airflow to 3.2.2.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Airflow	Affected <3.2.2	Fixed in 3.2.2
PyPIapache-airflow`pkg:pypi/apache-airflow`Other threats	Affected <3.2.2	Fixed in 3.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Airflow to version 3.2.2 or later. This version includes fixes that properly mask nested sensitive keys in rendered template fields, preventing exposure of plaintext secrets. Users who have already upgraded for CVE-2025-68438 should still apply this update to cover nested key paths. No other specific mitigations are indicated.

Description

CVE-2026-42360 is a medium severity vulnerability in Apache Airflow affecting versions prior to 3.2.2. It involves exposure of sensitive information due to improper masking of nested sensitive keys (such as password, token, secret, api_key) in rendered JSON templates when the rendered field length exceeds a configured limit. Authenticated users with permission to read rendered template fields could access plaintext secret values that should have been masked. This issue is a variant of a previously addressed vulnerability (CVE-2025-68438) but affects nested key paths. Users should upgrade to Apache Airflow 3.2.2 or later to remediate this issue.

Impact

Sensitive information such as passwords, tokens, secrets, and API keys nested within JSON templates may be exposed in plaintext to authenticated users with permission to read rendered template fields. This could lead to unauthorized disclosure of credentials or secrets, potentially compromising confidentiality. The vulnerability does not affect integrity or availability. Exploitation requires authenticated access with specific permissions.

Summary

Apache Airflow versions before 3.2.2 contain a vulnerability where nested sensitive keys inside JSON template structures are not properly masked if the rendered template field exceeds the '[core] max_templated_field_length' setting. The system stringifies the structure before redaction, losing the context of nested keys and resulting in plaintext sensitive data being stored in 'rendered_fields'. An authenticated user with read access to rendered template fields can retrieve these secret values. This vulnerability is a variant of CWE-200 and related to a prior fix for user-registered mask_secret() patterns (CVE-2025-68438) that did not cover nested sensitive keys. The fix is included starting in Apache Airflow 3.2.2.

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 10 Jul 2026, 09:54 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats