Airflow versions before 2.11.1 have a vulnerability that allows authenticated users with audit log access to see sensitive values in audit logs which they should not see. When sensitive connection parameters were set via airflow CLI, values of those variables appeared in the audit log and were stored unencrypted in the Airflow database. While this risk is limited to users with audit log access, it is recommended to upgrade to Airflow 2.11.1 or a later version, which addresses this issue. Users who previously used the CLI to set connections should manually delete entries with those connection sensitive values from the log table. This is similar but not the same issue as CVE-2024-50378
CVE-2025-27555
This medium-severity CVE scores 6.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(low)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
February 24, 2026
Last Modified
June 17, 2026
References (2)
- security@apachehttps://github.com/apache/airflow/pull/61882
- security@apachehttps://lists.apache.org/thread/nxovkp319jo8vg498gql1yswtb2frbkw
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:12 UTCEPSS rescore
- 2026-07-27 13:34 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS p95CRITICAL
- CVE-2018-11716EG 9.8EPSS p96CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8CRITICAL
- CVE-2018-1117NVD 5.0EG 9.8CRITICAL
- CVE-2018-11320EG 9.8CRITICAL
- CVE-2018-1000123EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2025-27555?
When was CVE-2025-27555 disclosed?
Is CVE-2025-27555 actively exploited?
What is the CVSS score of CVE-2025-27555?
How do I remediate CVE-2025-27555?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-27555
Is Your Infrastructure Affected by CVE-2025-27555?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.