CVE-2026-45192: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Airflow
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.
AI Analysis
Technical Summary
CVE-2026-45192 is an information exposure vulnerability in Apache Airflow affecting the GET /api/v2/connections/{connection_id} REST API endpoint. Authenticated users with Connection-read permission could retrieve plaintext secrets stored in the Connection's extra JSON blob under field names not included in the redaction allowlist (DEFAULT_SENSITIVE_FIELDS). For example, Slack-provider credential fields were exposed. This vulnerability impacts deployments that store credentials inline in the extra field and allow multiple users Connection-read access. The issue is resolved in Apache Airflow 3.2.2 and later versions. As an additional mitigation, storing sensitive credentials in a secret backend rather than inline in the extra field is recommended.
Potential Impact
An authenticated user with Connection-read permission can access sensitive credential information in plaintext that should have been redacted, potentially leading to unauthorized disclosure of secrets such as Slack credentials. This could compromise confidentiality of stored credentials but does not affect integrity or availability. The impact is limited to deployments that store credentials in the extra field and grant read access to multiple users.
Mitigation Recommendations
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.
CVE-2026-45192: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Airflow
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.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45192 is an information exposure vulnerability in Apache Airflow affecting the GET /api/v2/connections/{connection_id} REST API endpoint. Authenticated users with Connection-read permission could retrieve plaintext secrets stored in the Connection's extra JSON blob under field names not included in the redaction allowlist (DEFAULT_SENSITIVE_FIELDS). For example, Slack-provider credential fields were exposed. This vulnerability impacts deployments that store credentials inline in the extra field and allow multiple users Connection-read access. The issue is resolved in Apache Airflow 3.2.2 and later versions. As an additional mitigation, storing sensitive credentials in a secret backend rather than inline in the extra field is recommended.
Potential Impact
An authenticated user with Connection-read permission can access sensitive credential information in plaintext that should have been redacted, potentially leading to unauthorized disclosure of secrets such as Slack credentials. This could compromise confidentiality of stored credentials but does not affect integrity or availability. The impact is limited to deployments that store credentials in the extra field and grant read access to multiple users.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-10T21:43:28.304Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e79e29bf47b50cd4b6f
Added to database: 06/01/2026, 09:18:49 UTC
Last enriched: 07/08/2026, 13:38:33 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 146
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.