CyberSecBulletin
CVE-2025-66236NVD status: Analyzed

Apache Airflow: Insertion of Sensitive Information into Log File

Published Updated By the CyberSecBulletin desk

CVE-2025-66236 is a high-severity insertion of sensitive information into log file vulnerability in Apache Airflow from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.2.0 as the first without the flaw, so updating Apache Airflow to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Apache Airflow to 3.2.0 or a later version.
  2. Update Airflow to 3.2.0 or a later version.
  3. Read the advisory on lists.apache.org for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache Airflow3.0.0 up to, but not including, 3.2.03.2.0
ApacheAirflow3.0.0 up to, but not including, 3.2.03.2.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).

Official description

Before Airflow 3.2.0, it was unclear that secure Airflow deployments require the Deployment Manager to take appropriate actions and pay attention to security details and security model of Airflow. Some assumptions the Deployment Manager could make were not clear or explicit enough, even though Airflow's intentions and security model of Airflow did not suggest different assumptions. The overall security model [1], workload isolation [2], and JWT authentication details [3] are now described in more detail. Users concerned with role isolation and following the Airflow security model of Airflow are advised to upgrade to Airflow 3.2, where several security improvements have been implemented. They should also read and follow the relevant documents to make sure that their deployment is secure enough. It also clarifies that the Deployment Manager is ultimately responsible for securing your Airflow deployment. This had also been communicated via Airflow 3.2.0 Blog announcement [4]. [1] Security Model: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [2] Workload isolation: https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html [3] JWT Token authentication: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [4] Airflow 3.2.0 Blog announcement: https://airflow.apache.org/blog/airflow-3.2.0/ Users are recommended to upgrade to version 3.2.0, which fixes this issue.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Other vulnerabilities in Apache Airflow

All Apache Airflow vulnerabilities

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.