CVE-2026-22872

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.7% (52nd 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
Elevated

Also known asEUVD-2026-33729 (ENISA EUVD) · GHSA-qjjm-7j9w-pw72 (GitHub Security Advisories) · GO-2026-5584 (OSV.dev)Source: ENISA EUVD

9.1EG
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.7%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Capsule is a multi-tenancy and policy-based framework for Kubernetes. The Capsule Controller runs with cluster-admin privileges. Although the TenantResource RawItems processing logic forcibly sets the namespace, this is ineffective for cluster-scoped resources. Prior to version 0.13.0, tenant administrators can leverage the Controller's elevated privileges to create cluster-scoped resources (such as ClusterRole and ValidatingWebhookConfiguration) that they cannot create directly, achieving cross-tenant privilege escalation and cluster-level attacks. The attack vector has a few limiting factors. This attack requires Tenant Owner privileges and requires Capsule Controller running with cluster-admin privileges (default configuration). Additionally, some clusters may have additional admission controllers blocking malicious resources. Version 0.13.0 patches this issue.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.7%
EPSS %ILE
52nd
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 28, 2026

Last Modified

July 22, 2026

Advisory Details (2)

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

TenantResource RawItems Cluster-Scoped Resource Creation Vulnerability · Advisory · projectcapsule/capsule · GitHub

https://github.com/projectcapsule/capsule/security/advisories/GHSA-qjjm-7j9w-pw72
GitHub release Patch Available

v0.13.0

Patch available: projectcapsule/capsule v0.13.0

https://github.com/projectcapsule/capsule/releases/tag/v0.13.0

Vendor Advisories for CVE-2026-22872(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/projectcapsule/capsule @ 0.13.0 (fixes < 0.13.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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/projectcapsule/capsule—
  • every version up to 0.13.0: fixed in 0.13.0
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-22872?
CVE-2026-22872 is a critical-severity vulnerability; its CVE record was published on May 28, 2026. Capsule is a multi-tenancy and policy-based framework for Kubernetes. The Capsule Controller runs with cluster-admin privileges. Although the TenantResource RawItems processing logic forcibly sets the namespace, this is ineffective for cluster-scoped resources. Prior to version 0.13.0, tenant…
When was the CVE record for CVE-2026-22872 published?
The CVE record for CVE-2026-22872 was published on May 28, 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-22872 actively exploited?
CVE-2026-22872 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22872?
CVE-2026-22872 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-22872?
A fix for CVE-2026-22872 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-22872 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-22872

Explore →

Is Your Infrastructure Affected by CVE-2026-22872?

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