CVE-2026-49486

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Apache Airflow FTP provider's FTPSHook.get_conn() created an ftplib.FTP_TLS connection but never called prot_p(), so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using FTPSHook or FTPSFileTransmitOperator to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to 3.15.1 or later, which issues PROT P to encrypt the data channel.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Call prot_p() in FTPSHook so the FTPS data channel is protected

Fix merged in apache/airflow PR #67946 on 2026-06-03 — awaiting tagged release

https://github.com/apache/airflow/pull/67946

Vendor Advisories for CVE-2026-49486(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
apache-airflow-providers-ftp1.0.0 ... 3.9.1rc1 (92 versions)3.15.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 106× 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.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 00:45 UTCEG score recompute
  4. 2026-08-25 00:45 UTCGHSA enrichment
  5. 2026-08-24 13:06 UTCEG score recompute
  6. 2026-08-24 13:06 UTCGHSA enrichment
  7. 2026-08-23 21:25 UTCGHSA enrichment
  8. 2026-08-23 09:50 UTCEG score recompute
  9. 2026-08-23 09:50 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 22:17 UTCGHSA enrichment
  12. 2026-08-22 09:49 UTCEG score recompute
  13. 2026-08-22 09:49 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 17:46 UTCGHSA enrichment
  16. 2026-08-21 06:12 UTCEG score recompute
  17. 2026-08-21 06:12 UTCGHSA enrichment
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 18:33 UTCGHSA enrichment
  20. 2026-08-20 06:59 UTCEG score recompute
  21. 2026-08-20 06:59 UTCGHSA enrichment
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-19 12:38 UTCGHSA enrichment
  24. 2026-08-19 01:04 UTCEG score recompute
  25. 2026-08-19 01:04 UTCGHSA enrichment
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 07:35 UTCGHSA enrichment
  4. 2026-08-16 20:01 UTCEG score recompute
  5. 2026-08-16 20:01 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 07:31 UTCEG score recompute
  8. 2026-08-16 07:31 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 19:58 UTCGHSA enrichment
  11. 2026-08-15 08:22 UTCEG score recompute
  12. 2026-08-15 08:22 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 20:43 UTCGHSA enrichment
  15. 2026-08-14 09:09 UTCEG score recompute
  16. 2026-08-14 09:09 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 21:35 UTCGHSA enrichment
  19. 2026-08-13 10:02 UTCGHSA enrichment
  20. 2026-08-12 22:27 UTCEG score recompute
  21. 2026-08-12 22:27 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 10:54 UTCGHSA enrichment
  24. 2026-08-11 23:20 UTCEG score recompute
  25. 2026-08-11 23:20 UTCGHSA enrichment
  26. 2026-08-11 11:46 UTCGHSA enrichment
  27. 2026-08-11 00:12 UTCEG score recompute
  28. 2026-08-11 00:12 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 12:38 UTCGHSA enrichment
  31. 2026-08-10 01:04 UTCEG score recompute
  32. 2026-08-10 01:04 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 13:30 UTCGHSA enrichment
  35. 2026-08-09 01:57 UTCEG score recompute
  36. 2026-08-09 01:57 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-08 14:23 UTCGHSA enrichment
  39. 2026-08-08 02:49 UTCEG score recompute
  40. 2026-08-08 02:49 UTCGHSA enrichment
  41. 2026-08-07 15:15 UTCGHSA enrichment
  42. 2026-08-07 03:41 UTCGHSA enrichment
  43. 2026-08-06 16:08 UTCEG score recompute
  44. 2026-08-06 16:08 UTCGHSA enrichment
  45. 2026-08-06 13:47 UTCEPSS rescore
  46. 2026-08-06 04:32 UTCEG score recompute
  47. 2026-08-06 04:32 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-05 16:58 UTCGHSA enrichment
  50. 2026-08-05 02:36 UTCEG score recompute
  51. 2026-08-05 02:36 UTCGHSA enrichment
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 15:01 UTCEG score recompute
  54. 2026-08-04 15:01 UTCGHSA enrichment
  55. 2026-08-04 10:39 UTCEPSS rescore
  56. 2026-08-04 01:31 UTCGHSA enrichment
  57. 2026-08-03 13:57 UTCEG score recompute
  58. 2026-08-03 13:57 UTCGHSA enrichment
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-02 22:42 UTCGHSA enrichment
  61. 2026-08-02 11:08 UTCEG score recompute
  62. 2026-08-02 11:08 UTCGHSA enrichment
  63. 2026-08-02 02:27 UTCEPSS rescore
  64. 2026-08-01 23:34 UTCGHSA enrichment
  65. 2026-08-01 12:00 UTCEG score recompute
  66. 2026-08-01 12:00 UTCGHSA enrichment
  67. 2026-08-01 04:16 UTCEPSS rescore
  68. 2026-08-01 00:26 UTCGHSA enrichment
  69. 2026-07-31 12:52 UTCGHSA enrichment
  70. 2026-07-31 01:17 UTCEG score recompute
  71. 2026-07-31 01:17 UTCGHSA enrichment
  72. 2026-07-30 16:28 UTCEPSS rescore
  73. 2026-07-30 13:42 UTCEG score recompute
  74. 2026-07-30 13:42 UTCGHSA enrichment
  75. 2026-07-30 01:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-49486?
CVE-2026-49486 is a high vulnerability published on June 26, 2026. The Apache Airflow FTP provider's FTPSHook.getconn() created an ftplib.FTPTLS connection but never called prot_p(), so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using FTPSHook or FTPSFileTransmitOperator to move files over FTPS…
When was CVE-2026-49486 disclosed?
CVE-2026-49486 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49486 actively exploited?
CVE-2026-49486 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49486?
CVE-2026-49486 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49486?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49486, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49486

Explore →

Is Your Infrastructure Affected by CVE-2026-49486?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.