CVE-2025-68675VulnerabilityPublished 16 Jan 2026Updated 24 Feb 2026

CVE-2025-68675: Apache Airflow · Sensitive Data in Logs

Affects Apache AirflowSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 3.1.6 or 2.11.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 1.8% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.1.6, 2.11.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 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-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 and apache-airflow to 3.1.6 or 2.11.1.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Airflow	Affected >=3.0.0 <3.1.6 <2.11.1	Fixed in 3.1.6 2.11.1
PyPIapache-airflow`pkg:pypi/apache-airflow`Other threats	Affected <2.11.1 <3.1.6	Fixed in 2.11.1 3.1.6

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 if using Airflow 3.x, or to 2.11.1 or later if using Airflow 2.x, as these versions include fixes that mask proxy credentials in logs. 2. Audit existing log files for any exposure of proxy credentials and immediately rotate any credentials found to be compromised. 3. Implement strict access controls on log storage and transmission channels to minimize unauthorized access to sensitive log data. 4. Review and sanitize any custom logging configurations or plugins that might bypass default masking behavior. 5. Employ centralized log management solutions with encryption and role-based access controls to protect log integrity and confidentiality. 6. Educate DevOps and security teams about the risks of logging sensitive information and enforce secure coding and configuration practices. 7. Monitor network traffic and proxy usage for anomalous activities that could indicate misuse of leaked credentials. 8. Consider using environment variables or secure vaults for storing sensitive connection information instead of embedding credentials directly in proxy URLs.

Description

In Apache Airflow versions before 3.1.6, and 2.11.1 the proxies and proxy fields within a Connection may include proxy URLs containing embedded authentication information. These fields were not treated as sensitive by default and therefore were not automatically masked in log output. As a result, when such connections are rendered or printed to logs, proxy credentials embedded in these fields could be exposed. Users are recommended to upgrade to 3.1.6 or later for Airflow 3, and 2.11.1 or later for Airflow 2 which fixes this issue

Impact

The primary impact of CVE-2025-68675 is the compromise of confidentiality due to the exposure of proxy authentication credentials in log files. Organizations running vulnerable versions of Apache Airflow risk unauthorized access to proxy services if attackers gain access to logs or intercept log data. This can lead to further network reconnaissance, unauthorized data access, or lateral movement within internal networks. Since Airflow is often used in critical data pipelines and cloud environments, leaked credentials could undermine the security of connected systems and services. The vulnerability does not affect integrity or availability directly but can facilitate subsequent attacks that do. The ease of exploitation—requiring no authentication or user interaction—combined with the widespread use of Airflow in enterprises and cloud providers, elevates the threat level. Exposure of proxy credentials may also violate compliance requirements related to credential management and data protection, potentially leading to regulatory penalties and reputational damage.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (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 1 Mar 2026, 06:10 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats