CVE-2026-22039

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 2026-01-27. NVD baseline CVSS 9.9; sources differ by 0.0.

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

Also known asEUVD-2026-4811 (ENISA EUVD) · GHSA-8p9x-46gm-qfx2 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3 have a critical authorization boundary bypass in namespaced Kyverno Policy apiCall. The resolved urlPath is executed using the Kyverno admission controller ServiceAccount, with no enforcement that the request is limited to the policy’s namespace. As a result, any authenticated user with permission to create a namespaced Policy can cause Kyverno to perform Kubernetes API requests using Kyverno’s admission controller identity, targeting any API path allowed by that ServiceAccount’s RBAC. This breaks namespace isolation by enabling cross-namespace reads (for example, ConfigMaps and, where permitted, Secrets) and allows cluster-scoped or cross-namespace writes (for example, creating ClusterPolicies) by controlling the urlPath through context variable substitution. Versions 1.16.3 and 1.15.3 contain a patch for the vulnerability.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
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
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

January 27, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Oct 27, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Kyverno Cross-Namespace Privilege Escalation via Policy apiCall · Advisory · kyverno/kyverno · GitHub

https://github.com/kyverno/kyverno/security/advisories/GHSA-8p9x-46gm-qfx2
GitHub commit

commit eba60fa856c7 (kyverno/kyverno)

Fix landed in kyverno/kyverno commit eba60fa856c7 — awaiting tagged release

https://github.com/kyverno/kyverno/commit/eba60fa856c781bcb9c3be066061a3df03ae4e3e
GitHub commit

commit e0ba4de4f1e0 (kyverno/kyverno)

Fix landed in kyverno/kyverno commit e0ba4de4f1e0 — awaiting tagged release

https://github.com/kyverno/kyverno/commit/e0ba4de4f1e0ca325066d5095db51aec45b1407b

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/kyverno/kyverno @ 1.15.3 (fixes < 1.15.3)—ghsa
gogithub.com/kyverno/kyverno @ 1.16.3 (fixes >= 1.16.0-rc.1, < 1.16.3)—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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/kyverno/kyverno—
  • every version up to 1.15.3: fixed in 1.15.3
  • 1.16.0-rc.1 up to 1.16.3: fixed in 1.16.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 58× 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 99 of 219 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-22039?
CVE-2026-22039 is a critical-severity vulnerability; its CVE record was published on January 27, 2026. Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3 have a critical authorization boundary bypass in namespaced Kyverno Policy apiCall. The resolved urlPath is executed using the Kyverno admission controller ServiceAccount, with no…
When was the CVE record for CVE-2026-22039 published?
The CVE record for CVE-2026-22039 was published on January 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-22039 actively exploited?
CVE-2026-22039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22039?
CVE-2026-22039 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-22039?
A fix for CVE-2026-22039 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-22039?

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