Apache Airflow's Config API did not mask team-scoped sensitive configuration values in multi-team deployments. When an administrator has enabled multi-team mode and exposed the Config API, an authenticated Viewer holding only configuration-read access — with no prior access to the secret — could read a team-scoped Celery broker URL, including its embedded credentials, in cleartext, while the equivalent global option was correctly masked. The secrets masker matched only base section and option names and did not normalize team-prefixed sections before the sensitivity check (CWE-200). This is a distinct masker bypass from CVE-2026-48828 and CVE-2026-48892: deployments that upgraded to apache-airflow 3.3.0 to address those issues remain affected by this team-scoped variant. Users are advised to upgrade to apache-airflow 3.3.1 or later, which normalizes team-scoped sections before masking.
CVE-2026-65017
Score 6.5 from GitHub Security Advisory published 2026-08-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.
- 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(high)
- EG Risk
- 29(Track)EG Risk 29/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%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 14, 2026
Advisory Details (4)
Auto-updated Aug 13, 2026Hide team scoped values of options registered as sensitive
Fix merged in apache/airflow PR #70755 on 2026-08-04 — awaiting tagged release
https://github.com/apache/airflow/pull/70755Vendor Advisories for CVE-2026-65017(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 32× 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-08-20 23:07 UTCEG score recompute
- 2026-08-20 23:07 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:24 UTCEG score recompute
- 2026-08-19 22:24 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 21:39 UTCEG score recompute
- 2026-08-18 21:39 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:48 UTCEG score recompute
- 2026-08-17 20:48 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:04 UTCEG score recompute
- 2026-08-16 20:04 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-15 19:20 UTCEG score recompute
- 2026-08-15 19:20 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:35 UTCGHSA enrichment
- 2026-08-14 14:20 UTCEG score recompute
- 2026-08-14 14:20 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:36 UTCGHSA enrichment
- 2026-08-13 12:27 UTCEG score recompute▲ 6.50
- 2026-08-13 12:27 UTCGHSA enrichment
Show 7 moreShow fewer
- 2026-08-13 12:26 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-08-12 21:01 UTCGHSA enrichment
- 2026-08-12 21:00 UTCNVD update
- 2026-08-12 16:40 UTCMITRE cvelistV5
- 2026-08-12 16:33 UTCNVD update
- 2026-08-12 15:36 UTCEG score recompute
- 2026-08-12 15:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-65017?
When was CVE-2026-65017 disclosed?
Is CVE-2026-65017 actively exploited?
What is the CVSS score of CVE-2026-65017?
How do I remediate CVE-2026-65017?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65017
Is Your Infrastructure Affected by CVE-2026-65017?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.