CVE-2026-27173

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-05-19. NVD baseline CVSS 8.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.7Exploit: NoneExposed: 0

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

JWT tokens that were used by workers in Kubernetes Executors have been exposed to users who had read only access to Kuberentes Pods. This could allow users with just read-only access to perform actions that were only available to running tasks via Task SDK and potentially allow to modify state of Airflow Database for tasks.

CVSS v3
8.7
EG Score
8.7(medium)
EPSS
5.2%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated May 19, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-27173: Apache Airflow CNCF Kubernetes provider: JWT Token Exposure in KubernetesExecutor Command-Line Arguments

http://www.openwall.com/lists/oss-security/2026/05/19/35
generic

Two-token mechanism for task execution to prevent token expiration while tasks wait in executor queues by anishgirianish · Pull Request #60108 · apache/airflow · GitHub

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

Vendor Advisories for CVE-2026-27173(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-cncf-kubernetes1.0.0 ... 9.0.1rc1 (215 versions)10.17.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 61× 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 144 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-27173?
CVE-2026-27173 is a high vulnerability published on May 19, 2026. JWT tokens that were used by workers in Kubernetes Executors have been exposed to users who had read only access to Kuberentes Pods. This could allow users with just read-only access to perform actions that were only available to running tasks via Task SDK and potentially allow to modify state of…
When was CVE-2026-27173 disclosed?
CVE-2026-27173 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27173 actively exploited?
CVE-2026-27173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-27173?
CVE-2026-27173 has a CVSS v3.1 base score of 8.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-27173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27173, 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-27173

Explore →

Is Your Infrastructure Affected by CVE-2026-27173?

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