CVE-2026-49298

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

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

A bug in Apache Airflow's KubernetesExecutor caused JWT tokens used by worker pods to authenticate against the Execution API to be passed to the worker container as command-line arguments visible in the pod spec. An authenticated UI/API user with Kubernetes read-only access to the cluster (e.g. pods/get in the Airflow namespace) could harvest the JWT from kubectl describe pod output and then call state-mutating Execution API endpoints — triggering Dag runs, clearing runs, reading or writing Variables / Connections / XComs — as if they were a running task. Affects deployments using the KubernetesExecutor. Users are advised to upgrade to apache-airflow 3.2.2 or later. This is the airflow-core half of the same vulnerability addressed by CVE-2026-27173, which shipped the apache-airflow-providers-cncf-kubernetes side of the fix. Deployments that already upgraded apache-airflow-providers-cncf-kubernetes to 10.17.0 or later per the CVE-2026-27173 advisory should additionally upgrade apache-airflow to 3.2.2 or later to close the core-side surface — the two fixes are complementary, not duplicates.

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

Published

June 1, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic
https://lists.apache.org/thread/wo09vrks8189dzsot39rvrx3vnx102tt
github_pr

Two-token mechanism for task execution to prevent token expiration while tasks wait in executor queues

Fix merged in apache/airflow PR #60108 on 2026-04-23 — awaiting tagged release

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

Vendor Advisories for CVE-2026-49298(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-core3.0.0 ... 3.2.2rc3 (69 versions)3.2.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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 194 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-49298?
CVE-2026-49298 is a high vulnerability published on June 1, 2026. A bug in Apache Airflow's KubernetesExecutor caused JWT tokens used by worker pods to authenticate against the Execution API to be passed to the worker container as command-line arguments visible in the pod spec. An authenticated UI/API user with Kubernetes read-only access to the cluster (e.g.…
When was CVE-2026-49298 disclosed?
CVE-2026-49298 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49298 actively exploited?
CVE-2026-49298 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 59.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49298?
CVE-2026-49298 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49298?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49298, 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-49298

Explore →

Is Your Infrastructure Affected by CVE-2026-49298?

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

Start Free Scan →Browse All CVEs