CVE-2026-61672

HIGHPre-NVD 7.17.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to 0.13.7, ForbiddenListSpec.ExactMatch in pkg/api/forbidden_list.go sorts denied metadata keys case-insensitively and then uses sort.SearchStrings, which assumes byte-order sorting. When an administrator's forbidden list mixes capitalized and lowercase keys or otherwise has different case-insensitive and byte ordering, the binary search can return false for a key that is present. An authenticated tenant owner can then pass the missed key through api.ValidateForbidden and bypass configured namespace, Service, or delegated node metadata restrictions, potentially influencing cluster policies, network exposure, or scheduling outside the tenant boundary. Uniformly lowercase lists whose two orderings coincide are not affected. This issue is fixed in version 0.13.7.

CVSS v3
7.1
EG Score
7.1(low)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
github_release Patch Available

v0.13.7

Patch available: projectcapsule/capsule v0.13.7

https://github.com/projectcapsule/capsule/releases/tag/v0.13.7
github_pr

feat(rules): add service enforcement rules

Fix merged in projectcapsule/capsule PR #1982 on 2026-06-24 — awaiting tagged release

https://github.com/projectcapsule/capsule/pull/1982
github Patch Available🟡 PoC Available

Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement because `ForbiddenListSpec.ExactMatch` runs `sort.SearchStrings` (byte order) over a slice sorted case-insensitively · Advisory · projectcapsule/capsule · GitHub

https://github.com/projectcapsule/capsule/security/advisories/GHSA-gjw4-3v3v-rqxg

Vendor Advisories for CVE-2026-61672(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 17:26 UTCEG score recompute
  2. 2026-09-18 16:39 UTCEG score recompute
  3. 2026-09-18 16:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61672?
CVE-2026-61672 is a high vulnerability published on September 18, 2026. Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to 0.13.7, ForbiddenListSpec.ExactMatch in pkg/api/forbidden_list.go sorts denied metadata keys case-insensitively and then uses sort.SearchStrings, which assumes byte-order sorting. When an administrator's forbidden list…
When was CVE-2026-61672 disclosed?
CVE-2026-61672 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61672 actively exploited?
CVE-2026-61672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.3% of all scored CVEs.
What is the CVSS score of CVE-2026-61672?
CVE-2026-61672 has a CVSS v3 base score of 7.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-61672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61672, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61672

Explore →

Is Your Infrastructure Affected by CVE-2026-61672?

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