CVE-2026-54523

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. A secondary CVSS source baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-66561 (ENISA EUVD) · GHSA-79gf-7frw-68m9 (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
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.5%CVSS: 9.6Exploit: 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. From 1.18.0 until 1.18.2, the NamespacedMutatingPolicy CEL compiler exposes the generator library to matchConditions, allowing a namespace-scoped policy to invoke generator.apply(namespace, resources) with an arbitrary target namespace. The validation in pkg/cel/policies/mpol/validate.go checks that the policy compiles but does not enforce namespace scope, and GenerateResources in pkg/cel/libs/context.go does not reject the cross-namespace target. A user who can create NamespacedMutatingPolicy objects in one namespace can cause the admission controller, operating with cluster-wide privileges, to create ConfigMaps, NetworkPolicies, Secrets, RoleBindings, and other resources in another namespace, enabling unauthorized modification and potential privilege escalation. This issue is fixed in version 1.18.2.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 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.5%
EPSS %ILE
40th
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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-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-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

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (6)

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

NamespacedMutatingPolicy generator.apply() namespace argument unvalidated in v1.18.1 - allows cross-namespace resource generation via admission controller · Advisory · kyverno/kyverno · GitHub

https://github.com/kyverno/kyverno/security/advisories/GHSA-79gf-7frw-68m9
GitHub commit

commit 657393744144 (kyverno/sdk)

Fix landed in kyverno/sdk commit 657393744144 — awaiting tagged release

https://github.com/kyverno/sdk/commit/6573937441443e1ba5af9fbb28d5c0f20297f9df
GitHub release Patch Available

v1.18.2

Patch available: kyverno/kyverno v1.18.2

https://github.com/kyverno/kyverno/releases/tag/v1.18.2
GitHub pull request

fix(gpol,mpol): enforce namespace boundary in generator.apply() (backport GHSA-79gf-7frw-68m9 to release-1.18)

Fix merged in kyverno/kyverno PR #16238 on 2026-06-05 — awaiting tagged release

https://github.com/kyverno/kyverno/pull/16238
GitHub commit

commit 5164bcdeda5b (kyverno/kyverno)

Fix landed in kyverno/kyverno commit 5164bcdeda5b — awaiting tagged release

https://github.com/kyverno/kyverno/commit/5164bcdeda5b57678bc2d7a03ecc2cbb02982dae
GitHub commit

commit 0919553c0ea1 (kyverno/kyverno)

Fix landed in kyverno/kyverno commit 0919553c0ea1 — awaiting tagged release

https://github.com/kyverno/kyverno/commit/0919553c0ea1904f8d891280c92018da97946a06

Vendor Advisories for CVE-2026-54523(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
gogithub.com/kyverno/kyverno @ 1.18.2 (fixes >= 1.18.0, <= 1.18.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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/kyverno/kyverno—
  • 1.18.0 up to 1.18.2: fixed in 1.18.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 66× 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 135 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 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-54523?
CVE-2026-54523 is a critical-severity vulnerability; its CVE record was published on August 26, 2026. Kyverno is a policy engine designed for cloud native platform engineering teams. From 1.18.0 until 1.18.2, the NamespacedMutatingPolicy CEL compiler exposes the generator library to matchConditions, allowing a namespace-scoped policy to invoke generator.apply(namespace, resources) with an arbitrary…
When was the CVE record for CVE-2026-54523 published?
The CVE record for CVE-2026-54523 was published on August 26, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-54523 actively exploited?
CVE-2026-54523 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54523?
CVE-2026-54523 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54523?
A fix for CVE-2026-54523 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54523 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-54523

Explore →

Is Your Infrastructure Affected by CVE-2026-54523?

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