# CVE-2026-30912: apache-airflow-core — Fixed in 3.2.0

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

# CVE-2026-30912 — apache-airflow-core

HIGH [Fix: apache/airflow#63028](https://github.com/apache/airflow/pull/63028)

CVE-2026-30912 is a high-severity (CVSS 7.5) CWE-668 vulnerability in apache-airflow-core. A fix is available for apache-airflow-core — see the affected versions and patch details below.

Apache Airflow: Exposing stack trace in case of constraint error

Also known asBIT-airflow-2026-30912[GHSA-w7cf-2pmc-5m4c](/vulnerability/GHSA-w7cf-2pmc-5m4c)PYSEC-2026-18PYSEC-2026-2361

Published

Apr 18, 2026

Updated

Nov 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-30912.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

0.00%0.42%0.84%1.26%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

1 pkg affected

🐍`apache-airflow-core`

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

## Description

In case of SQL errors, exception/stack trace of errors was exposed in API even if "api/expose\_stack\_traces" was set to false. That could lead to exposing additional information to potential attacker. Users are recommended to upgrade to Apache Airflow 3.2.0, which fixes the issue.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

🐍PyPI

`apache-airflow-core` 

all versions

3.2.0`pip install --upgrade 'apache-airflow-core==3.2.0'`

## Affected Products

1 product · 1 configurations

Application

`airflow`apache

< 3.2.0

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-airflow-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update apache-airflow-core to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-30912 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
    

## Frequently Asked Questions

In case of SQL errors, exception/stack trace of errors was exposed in API even if "api/expose\_stack\_traces" was set to false. That could lead to exposing additional information to potential attacker. Users are recommended to upgrade to Apache Airflow 3.2.0, which fixes the issue.

O3 Security · Impact-Aware SCA

### Is CVE-2026-30912 in your dependencies?

Find it across PyPI, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)