CVE-2026-58076

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-57315 (ENISA EUVD) · GHSA-8prw-8m6x-8w6f (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Apache Airflow's serialization layer reconstructed exception nodes by calling import_string() on a class name taken from the serialized blob and instantiating it with arguments from the same blob, with no restriction on what could be imported. An operator's executor_config reaches that branch, so a Dag author could place a value there that causes an arbitrary callable to be imported and invoked -- for example subprocess.check_output, or builtins.eval on the builtins-prefixed variant. The code runs in the Scheduler, which reconstructs serialized Dags in its normal loop with no request involved, and in the API server, on any authenticated read of the Dag such as GET /api/v2/dags/{dag_id}/details. Both are components the Airflow security model states must never execute Dag-author code, and both hold the metadata database credentials and the JWT signing secret. No non-default configuration is required. This is a different sink from CVE-2026-33264, which covered only the trigger branch of the same deserializer: deployments that upgraded in response to that advisory are still affected through the exception branch and must upgrade again. Users are advised to upgrade to apache-airflow 3.3.1 or later, which restricts the imported class to a subclass of BaseException.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 12, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
Patch available. Sources: github_pr.
Web page
https://www.cve.org/CVERecord?id=CVE-2026-33264
Web page
https://lists.apache.org/thread/t81p688t15jozxsng8521o60nh2kfsos
GitHub pull request

Restrict exception-node deserialization to known classes without importing the stored name

Fix merged in apache/airflow PR #68511 on 2026-08-05 — awaiting tagged release

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

Vendor Advisories for CVE-2026-58076(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipapache-airflow @ 3.3.1 (fixes >= 3.3.0, < 3.3.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
apache-airflow3.3.0, 3.3.1rc1, 3.3.1rc2
  • 3.3.0 up to 3.3.1: fixed in 3.3.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-58076?
CVE-2026-58076 is a high-severity vulnerability; its CVE record was published on August 12, 2026. Apache Airflow's serialization layer reconstructed exception nodes by calling import_string() on a class name taken from the serialized blob and instantiating it with arguments from the same blob, with no restriction on what could be imported. An operator's executor_config reaches that branch, so a…
When was the CVE record for CVE-2026-58076 published?
The CVE record for CVE-2026-58076 was published on August 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-58076 actively exploited?
CVE-2026-58076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58076?
CVE-2026-58076 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-58076?
A fix for CVE-2026-58076 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58076 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58076?

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

Book a Demo →Browse All CVEs