CVE-2025-68438: Apache Airflow · Information Exposure
Affects Apache AirflowSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.1.6 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 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-26.
What to do
Upgrade Apache Airflow to 3.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Airflow | Affected
| Fixed in
|
PyPIapache-airflowpkg:pypi/apache-airflowOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade Apache Airflow to version 3.1.6 or later immediately to apply the official fix that ensures proper masking of secrets in rendered templates. 2. Review and audit all DAG templates for embedded sensitive information and minimize the inclusion of secrets in templates where possible. 3. Implement strict access controls on the Airflow UI, limiting access to trusted personnel only and enforcing strong authentication mechanisms such as multi-factor authentication (MFA). 4. Regularly monitor Airflow logs and UI access patterns to detect any unauthorized or suspicious activity. 5. Use environment variables or secret management tools integrated with Airflow to handle sensitive data securely, avoiding hardcoding secrets in templates. 6. Educate developers and operators about secure template practices and the risks of exposing secrets in UI components. 7. Consider network segmentation or VPN access restrictions to limit exposure of the Airflow UI to internal or secure networks only. 8. If upgrading immediately is not feasible, temporarily restrict access to the Rendered Templates UI or disable features that render long template fields until patched.
Description
In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display. Users are recommended to upgrade to 3.1.6 or later, which fixes this issue