CVE-2026-45192: Apache Airflow · Information Exposure
Affects Apache AirflowSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.2.2 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.2.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Upgrade Apache Airflow and apache-airflow to 3.2.2.
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
Upgrade Apache Airflow to version 3.2.2 or later, where this vulnerability is fixed. Additionally, as a defense-in-depth measure, store sensitive credential values in a secret backend instead of embedding them in the Connection's extra JSON field. No vendor advisory explicitly states otherwise, so these are the recommended actions.
Description
A vulnerability in Apache Airflow's REST API endpoint /api/v2/connections/{connection_id} allows authenticated users with Connection-read permission to access sensitive credential information stored in the Connection's extra JSON blob if the field names are not in the redaction allowlist. This affects deployments that store credentials in the extra field and grant read access to multiple users. The issue is fixed in Apache Airflow version 3.2.2 and later. Operators are advised to upgrade and consider storing sensitive credentials in a secret backend as a defense-in-depth measure.