Apache Airflow error reporting may expose full kwargs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-65995: 0.89% estimated exploitation activity in the next 30 days; percentile 59.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.5rc1 and 2.11.1, and users are strongly advised to upgrade to prevent potential disclosure of sensitive information.

Published by the source

21 Feb 2026, 03:31 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gfw7-2v73-69wg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gfw7-2v73-69wg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-65995

Advisory: Apache Airflow error reporting may expose full kwargs
IDs: CVE-2025-65995, GHSA-gfw7-2v73-69wg
Record: https://patchnext.com/advisories/cve-2025-65995 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: apache-airflow 3.1.5rc1, 2.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI apache-airflow: affected < 2.11.1; >= 3.0.0b1, < 3.1.5rc1; fixed in 2.11.1, 3.1.5rc1

## Suggested inspection (read-only)
- `python -m pip show apache-airflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apache-airflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gfw7-2v73-69wg (OSV record GHSA-gfw7-2v73-69wg lists affected ranges: PyPI apache-airflow >=0 =3.0.0b1 <3.1.5rc1 (fixed))
- Verified: https://github.com/advisories/GHSA-gfw7-2v73-69wg (GitHub-reviewed advisory GHSA-gfw7-2v73-69wg lists affected ranges: PyPI apache-airflow >=0 =3.0.0b1 <3.1.5rc1)

Commands are suggestions: review each one before running it.