Skip to main content
VulnerabilityPublished Updated

CVE-2026-31987: Apache Airflow · Sensitive Data in Logs

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.2.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Apache Airflow to 3.2.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache AirflowAffected
  • >=3.0.0 <3.2.0
Fixed in
  • 3.2.0
PyPIapache/airflowpkg:pypi/apache/airflowOther threatsAffected
  • =3.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache Airflow version 3.2.0, which contains the fix for this vulnerability. No other mitigation or temporary workaround is indicated. Patch status is confirmed by vendor recommendation to upgrade.

Description

JWT Tokens used by tasks were exposed in logs. This could allow UI users to act as Dag Authors. Users are advised to upgrade to Airflow version that contains fix. Users are recommended to upgrade to version 3.2.0, which fixes this issue.

References

Community reviews

Loading reviews…