CVE-2022-24817

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-16. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-5436 (ENISA EUVD) · GHSA-vvmq-fwmg-2gjc (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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: 1.1%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flux2 is an open and extensible continuous delivery solution for Kubernetes. Flux2 versions between 0.1.0 and 0.29.0, helm-controller 0.1.0 to v0.19.0, and kustomize-controller 0.1.0 to v0.23.0 are vulnerable to Code Injection via malicious Kubeconfig. In multi-tenancy deployments this can also lead to privilege escalation if the controller's service account has elevated permissions. Workarounds include disabling functionality via Validating Admission webhooks by restricting users from setting the spec.kubeConfig field in Flux Kustomization and HelmRelease objects. Additional mitigations include applying restrictive AppArmor and SELinux profiles on the controller’s pod to limit what binaries can be executed. This vulnerability is fixed in kustomize-controller v0.23.0 and helm-controller v0.19.0, both included in flux2 v0.29.0

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 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
1.1%
EPSS %ILE
66th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

May 6, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Nov 6, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Improper kubeconfig validation allows arbitrary code execution · Advisory · fluxcd/flux2 · GitHub

https://github.com/fluxcd/flux2/security/advisories/GHSA-vvmq-fwmg-2gjc

Vendor Advisories for CVE-2022-24817(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/fluxcd/flux2 @ 0.29.0 (fixes >= 0.1.0, < 0.29.0)—ghsa
gogithub.com/fluxcd/helm-controller @ 0.19.0 (fixes >= 0.2.0, < 0.19.0)—ghsa
gogithub.com/fluxcd/kustomize-controller @ 0.23.0 (fixes >= 0.1.0, < 0.23.0)—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

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/fluxcd/flux2—
  • 0.1.0 up to 0.29.0: fixed in 0.29.0
—
github.com/fluxcd/helm-controller—
  • 0.2.0 up to 0.19.0: fixed in 0.19.0
—
github.com/fluxcd/kustomize-controller—
  • 0.1.0 up to 0.23.0: fixed in 0.23.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 45× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 256 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 156 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-24817?
CVE-2022-24817 is a critical-severity vulnerability; its CVE record was published on May 6, 2022. Flux2 is an open and extensible continuous delivery solution for Kubernetes. Flux2 versions between 0.1.0 and 0.29.0, helm-controller 0.1.0 to v0.19.0, and kustomize-controller 0.1.0 to v0.23.0 are vulnerable to Code Injection via malicious Kubeconfig. In multi-tenancy deployments this can also…
When was the CVE record for CVE-2022-24817 published?
The CVE record for CVE-2022-24817 was published on May 6, 2022. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-24817 actively exploited?
CVE-2022-24817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24817?
CVE-2022-24817 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2022-24817?
A fix for CVE-2022-24817 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-24817 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-2022-24817

Explore →

Is Your Infrastructure Affected by CVE-2022-24817?

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