Skip to main content
VulnerabilityPublished

CVE-2026-25219: Apache Airflow · Information Exposure

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.1.8 when convenient.

Data as of 30 Oct 2026, 11:34 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 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 24 Oct 2026.

What to do

Upgrade Apache Airflow and apache-airflow to 3.1.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache AirflowAffected
  • <3.1.8
Fixed in
  • 3.1.8
PyPIapache-airflowpkg:pypi/apache-airflowOther threatsAffected
  • <3.1.8
Fixed in
  • 3.1.8

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

AI-suggested

Upgrade Apache Airflow to version 3.2.0 or later, where the sensitive connection properties are properly masked. Since this is a cloud service, the vendor manages remediation for hosted instances, but self-hosted deployments must apply the update. Check the official Apache Airflow advisory for the latest remediation guidance.

Description

The `access_key` and `connection_string` connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data. If you used Azure Service Bus connection with those values set or if you have other connections with those values storing sensitve values, you should upgrade Airflow to 3.1.8

References

Community reviews

Loading reviews…