CVE-2026-32241

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.8% (86th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-16771 (ENISA EUVD)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: 2.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flannel is a network fabric for containers, designed for Kubernetes. The Flannel project includes an experimental Extension backend that allows users to easily prototype new backend types. In versions of Flannel prior to 0.28.2, this Extension backend is vulnerable to a command injection that allows an attacker who can set Kubernetes Node annotations to achieve root-level arbitrary command execution on every flannel node in the cluster. The Extension backend's SubnetAddCommand and SubnetRemoveCommand receive attacker-controlled data via stdin (from the flannel.alpha.coreos.com/backend-data Node annotation). The content of this annotation is unmarshalled and piped directly to a shell command without checks. Kubernetes clusters using Flannel with the Extension backend are affected by this vulnerability. Other backends such as vxlan and wireguard are unaffected. The vulnerability is fixed in version v0.28.2. As a workaround, use Flannel with another backend such as vxlan or wireguard.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
41
EG Risk 41/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.
Exploitation2.8% × 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
2.8%
EPSS %ILE
86th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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: 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.

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

March 27, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 10, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Cross-node remote code execution via extension backend BackendData injection · Advisory · flannel-io/flannel · GitHub

Affected: version v0.28.2.

https://github.com/flannel-io/flannel/security/advisories/GHSA-vchx-5pr6-ffx2
GitHub release Patch Available

v0.28.2

Patch available: flannel-io/flannel v0.28.2

https://github.com/flannel-io/flannel/releases/tag/v0.28.2

Vendor Advisories for CVE-2026-32241(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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/flannel-io/flannel—
  • every version up to 0.28.2: fixed in 0.28.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 95 of 241 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  4. 2026-10-27 11:02 UTCEG score recompute
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  7. 2026-10-25 14:35 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  10. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  11. 2026-10-21 16:32 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  13. 2026-10-19 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  15. 2026-10-18 03:47 UTCEG score recompute
  16. 2026-10-17 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  17. 2026-10-17 15:53 UTCEG score recompute
  18. 2026-10-16 16:41 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  23. 2026-10-12 16:14 UTCEG score recompute
  24. 2026-10-11 19:56 UTCEG score recompute
  25. 2026-10-11 17:10 UTCEG score recompute
Show 70 more
  1. 2026-10-11 14:38 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  3. 2026-10-11 04:01 UTCOSV refresh
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  14. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  18. 2026-09-21 16:19 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 2.7% · 85th percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  32. 2026-09-02 14:11 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  33. 2026-09-02 13:14 UTCOSV refresh
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  42. 2026-08-24 14:17 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  50. 2026-08-16 09:57 UTCEG score recompute
  51. 2026-08-16 09:57 UTCVendor advisory
  52. 2026-08-16 02:14 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  53. 2026-08-15 01:30 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  54. 2026-08-14 19:25 UTCVendor advisory
  55. 2026-08-14 06:17 UTCEG score recompute
  56. 2026-08-14 06:17 UTCVendor advisory
  57. 2026-08-13 22:00 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  58. 2026-08-12 20:35 UTCEG score recompute
  59. 2026-08-12 20:35 UTCVendor advisory
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  61. 2026-08-11 20:44 UTCEG score recompute
  62. 2026-08-11 20:44 UTCVendor advisory
  63. 2026-08-11 03:46 UTCEG score recompute
  64. 2026-08-11 03:46 UTCVendor advisory
  65. 2026-08-11 00:00 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  66. 2026-08-10 07:54 UTCVendor advisory
  67. 2026-08-09 18:51 UTCEG score recompute
  68. 2026-08-09 13:46 UTCEPSS rescoreEPSS 2.7% · 84th percentile
  69. 2026-08-09 05:49 UTCEG score recompute
  70. 2026-08-09 05:49 UTCVendor advisory

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32241?
CVE-2026-32241 is a high-severity vulnerability; its CVE record was published on March 27, 2026. Flannel is a network fabric for containers, designed for Kubernetes. The Flannel project includes an experimental Extension backend that allows users to easily prototype new backend types. In versions of Flannel prior to 0.28.2, this Extension backend is vulnerable to a command injection that…
When was the CVE record for CVE-2026-32241 published?
The CVE record for CVE-2026-32241 was published on March 27, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-32241 actively exploited?
CVE-2026-32241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (86th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32241?
CVE-2026-32241 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-32241?
A fix for CVE-2026-32241 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32241 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-32241

Explore →

Is Your Infrastructure Affected by CVE-2026-32241?

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

Book a Demo →Browse All CVEs