Skip to content
Noroxi
CVE-2026-25219· NVD / CVE Program· CNA apache

Apache Airflow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access

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

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Apr 15, 2026
Updated
Jun 17, 2026
EPSS
0.6% · 44th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
apacheairflow

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache airflowbefore 3.2.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Airflow

    • before 3.1.8affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIapache-airflowbefore 3.1.83.1.8

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-13927The previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security riKEV
    99Now
  • CVE-2020-11978An issue was found in Apache Airflow versions 1.10.10 and below.KEV
    95Now
  • CVE-2021-38540Apache Airflow: Variable Import endpoint missed authentication check
    63This week
  • CVE-2022-40127Apache Airflow <2.4.0 has an RCE in a bash example
    61This week
  • CVE-2022-24288Apache Airflow: RCE in example DAGs
    58Plan
  • CVE-2020-11981An issue was found in Apache Airflow versions 1.10.10 and below.
    50Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Airflow3.1.8Vendor (CNA)
PyPI:apache-airflow3.1.8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-6843889 days apartApache Airflow: Secrets in rendered templates could contain parts of sensitive values when truncated
    30Monitor
  • CVE-2026-4235847 days apartApache Airflow: Variable masker depth-limit bypass returns cleartext nested secrets
    26Monitor
  • CVE-2026-4236047 days apartApache Airflow: Rendered template truncation bypasses nested sensitive-key masking
    26Monitor
  • CVE-2026-4519247 days apartApache Airflow: Incomplete Redaction of Sensitive Fields in Connection Extra API Response
    26Monitor
  • CVE-2026-2409865 days apartApache Airflow: Assigning single DAG permission leaked all DAGs Import Errors
    26Monitor
  • CVE-2026-4889283 days apartApache Airflow: Config API leaks per-key secrets backend kwargs - masker bypass on synthetic options
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records