Skip to content
Noroxi
NVD / CVE Program· CNA apache

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

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
  • 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.
  • Fixed version: Apache Software Foundation Apache Airflow 3.0.0, 3.1.8.

Low priority for now. Upgrade to Apache Software Foundation Apache Airflow 3.0.0, 3.1.8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

Published
Apr 15, 2026
Updated
Nov 3, 2026
EPSS
0.5% · 47th percentile

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.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-25219

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apacheairflow

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.0.0affected · semver
    • 3.0.0 and later · before 3.1.8affected · semver

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

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

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…KEV
    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

Published before and after this one in the same product

  • ← EarlierCVE-2026-33858Apr 13, 2026 · Apache Airflow: Unsafe Deserialization via Legacy Serialization Keys (__type/__var) Bypass in XCom API
    35Monitor
  • ← EarlierCVE-2025-54550Apr 15, 2026 · Apache Airflow: RCE by race condition in example_xcom dag
    32Monitor
  • Later →CVE-2026-31987Apr 16, 2026 · Apache Airflow: JWT token appearing in logs
    30Monitor

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.0.0Vendor (CNA)
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.

Patch and commit links

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

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

Not on record for this CVE: EPSS history · public bounty program.

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

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.

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/*"]}

References

Show all references (3 more)

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

All records