- Exploited
- No known exploitation
- Fix
- Fixed in apache-airflow 3.0.0 · apache-airflow-core 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: apache-airflow 3.0.0 · apache-airflow-core 3.4.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Airflow is affected by a flaw in its secrets masker, which failed to redact sensitive values stored under camelCase key names such as privateKey, connectionString, webhookUrl or accessKey in task logs, rendered template fields and API responses. A user who can read those logs or rendered templates, but should not have access to the credentials, could read them in cleartext.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Apache Airflow's secrets masker matched sensitive key names only in their snake_case form, so values stored under camelCase keys such as privateKey, connectionString, webhookUrl or accessKey — for example in a Connection's extra or a Variable — were not redacted in task logs, rendered template fields or API responses. A user who can read task logs or rendered templates, but is not meant to see those credentials, could read them in cleartext. Users are advised to upgrade to apache-airflow 3.4.0 or later. Airflow 2.x is also affected; Airflow 2 has reached end of life and will not receive a fix, so Airflow 2 users should upgrade to Apache Airflow 3.4.0 or later.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach16/20apache-airflow: 1.5M downloads a week
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 39 if advisories confirm default setups are exposed
Impact
- Widely used
apache-airflow has 1.5m weekly downloads.Source: pypistats.org
473 packages depend on apache-airflow.Source: deps.dev
What to do
Upgrade to a fixed version: apache-airflow 3.0.0 · apache-airflow-core 3.4.0.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- apache-airflowPyPI
From 2.1.0 · fixed in 3.0.0
Fixed in 3.0.0 (released Apr 22, 2025, 566 days before disclosure).
The latest release, 3.4.0, is not affected.
fixed in 3.4.0
Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
The latest release, 3.4.0, is not affected.
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111452
Is CVE-2026-111452 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-111452?
apache-airflow (PyPI): from 2.1.0 before 3.0.0. apache-airflow-core (PyPI): before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-111452?
Upgrade to a fixed version: apache-airflow 3.0.0 · apache-airflow-core 3.4.0.Source: cve.now feed data