Cyber Resilience

CVE-2026-30912

High

Published: 18 April 2026

Published
18 April 2026
Modified
21 April 2026
KEV Added
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0007 21.6th percentile
Risk Priority 15 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2026-30912 is a high-severity Exposure of Resource to Wrong Sphere (CWE-668) vulnerability in Apache Airflow. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified are NIST 800-53 SI-11 (Error Handling) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2026-30912 is a vulnerability in Apache Airflow that causes SQL error exception and stack traces to be exposed via the API, even when the "api/expose_stack_traces" configuration is set to false. This improper handling of error information affects Apache Airflow versions prior to 3.2.0 and is classified under CWE-668, with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact.

Remote attackers require only network access and face low complexity with no privileges or user interaction needed to exploit this issue. By triggering SQL errors in the API, unauthenticated adversaries can obtain stack traces, potentially revealing sensitive system details such as database structures, paths, or other internal information that aids further attacks.

Advisories recommend upgrading to Apache Airflow 3.2.0, which resolves the exposure. Relevant references include the fixing pull request at https://github.com/apache/airflow/pull/63028, an Apache mailing list announcement at https://lists.apache.org/thread/tp6kz1hnfb3zsrrtg19myo8x5x80w8r9, and an OSS-security mailing list post at http://www.openwall.com/lists/oss-security/2026/04/17/5.

EU & UK References

Vulnerability details

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…

more

fixes the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
Why these techniques?

Vulnerability in public-facing Apache Airflow API enables remote unauthenticated exploitation for stack trace disclosure (T1190); resulting exposure of paths, DB structures and internals directly supports System Information Discovery (T1082).

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

CVEs Like This One

CVE-2026-28779Same product: Apache Airflow
CVE-2026-40961Same product: Apache Airflow
CVE-2026-41084Same product: Apache Airflow
CVE-2025-66236Same product: Apache Airflow
CVE-2026-42359Same product: Apache Airflow
CVE-2026-32228Same product: Apache Airflow
CVE-2026-30911Same product: Apache Airflow
CVE-2025-54550Same product: Apache Airflow
CVE-2026-42252Same product: Apache Airflow
CVE-2024-56373Same product: Apache Airflow

Affected Assets

apache
airflow
≤ 3.2.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

SI-11 requires systems to handle errors and exceptions without compromising information security or revealing details that assist adversaries, directly preventing stack trace exposure in API error responses.

prevent

SI-2 mandates timely remediation of identified flaws, directly addressing this CVE by requiring upgrades to Apache Airflow 3.2.0 to eliminate the exposure.

prevent

SI-15 requires filtering of output to block sensitive information, mitigating potential leakage of stack traces and system details in API responses.

References