PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-65995 Apache CVE debrief

CVE-2025-65995 debrief based on the supplied source corpus. The vulnerability occurs in Airflow's DAG parsing error reporting in the UI, which could include full kwargs passed to operators, potentially exposing sensitive values. Affected users should assess exposure and upgrade to a fixed version to prevent disclosure of sensitive information. The issue has been fixed in Airflow 3.1.4 and 2.11.1. Users are strongly advised to upgrade to prevent potential disclosure of sensitive information.

Vendor
Apache
Product
Airflow
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-02-21
Original CVE updated
2026-11-03
Advisory published
2026-02-21
Advisory updated
2026-11-03

Who should care

Airflow users and administrators who have permission to view DAGs in the UI should assess exposure and upgrade to a fixed version to prevent potential disclosure of sensitive information

Why it matters

CVE-2025-65995: Airflow DAG parsing error reporting in the UI could include full kwargs passed to operators, potentially exposing sensitive values. Airflow users and administrators should assess exposure and upgrade to a fixed version to prevent disclosure.

  • Potential exposure of sensitive information in UI tracebacks
  • Need to upgrade to a fixed version to prevent disclosure
  • Review and update DAGs to avoid passing sensitive values as kwargs
  • Monitor Airflow UI for potential exposure of sensitive information

Technical summary

When a DAG failed during parsing, Airflow's error-reporting in the UI could include the full kwargs passed to the operators. If those kwargs contained sensitive values (such as secrets), they might be exposed in the UI tracebacks to authenticated users who had permission to view that DAG. The issue has been fixed in Airflow 3.1.4 and 2.11.1, and users are strongly advised to upgrade to prevent potential disclosure of sensitive information. This issue is related to the handling of DAGs in Airflow and the exposure of sensitive information in error reports.

Defensive priority

Upgrade to Airflow 3.1.4 or 2.11.1 to prevent potential disclosure of sensitive information

Recommended defensive actions

  • Upgrade to Airflow 3.1.4 or 2.11.1
  • Review and update DAGs to avoid passing sensitive values as kwargs
  • Monitor Airflow UI for potential exposure of sensitive information
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the issue, which has been fixed in Airflow 3.1.4 and 2.11.1. The issue occurs when a DAG fails during parsing, and Airflow's error-reporting in the UI could include the full kwargs passed to the operators. If those kwargs contained sensitive values (such as secrets), they might be exposed in the UI tracebacks to authenticated users who had permission to view that DAG.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-65995 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-65995

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-65995 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-65995

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.